Rant: Backbone, Angular, Meteor, Derby • Hacker News Board

Re: Rant: Backbone, Angular, Meteor, Derby

#161

Post by wilmoore » Sat, Jan 05, 2013, 9:27 PM UTC

jashkenas wrote: post #123

"It seems that most people today, when thinking about their next JS project, will use Backbone because it's the most popularl framework when it shouldn't be." (sic) Here's a long list of examples why maybe it should be: http://backbonejs.org/#examples In comparison, here's the public list of interesting apps built with Angular and Derby: http://builtwith.angularjs.org https://github.com/codeparty/derby/wiki/Community…

@jashkenas:

"... use Backbone because it's the most popularl framework when it shouldn't be."

You bring up a good point...to add to it, many people also choose to go with YUI, Dojo, EXT when Backbone or a list of small well curated libraries would have been a better fit.

Essentially, the problem isn't Backbone or any of the other libraries/frameworks...it's that there are a LOT of developers that can't seem to evaluate the available options effectively.

Re: Rant: Backbone, Angular, Meteor, Derby

#162

Post by wilmoore » Sat, Jan 05, 2013, 9:52 PM UTC

marknutter wrote: post #81

I've been using angular.js for a while now and there are a few reasons why I've really liked it: - dependency injection: because everything is injected, it makes writing isolated unit tests very easy. It also makes it very easy to swap functionality in and out without affecting other parts of the app. - two-way data-binding: most of the pain of being a javascript developer comes from managing and manipulating the DOM…

because everything is injected, it makes writing isolated unit tests very easy

I agree with that statement regarding DI; however, have you evaluated whether you NEED a DI container or just DI?

Angular forces you into a container even if you don't need it. Is that what you really wanted? If so, fine, just be sure :)

Re: Rant: Backbone, Angular, Meteor, Derby

#163

Post by tjholowaychuk » Sat, Jan 05, 2013, 10:21 PM UTC

dmvaldman wrote: post #129

jashkenas wrote: post #123

"It seems that most people today, when thinking about their next JS project, will use Backbone because it's the most popularl framework when it shouldn't be." (sic) Here's a long list of examples why maybe it should be: http://backbonejs.org/#examples In comparison, here's the public list of interesting apps built with Angular and Derby: http://builtwith.angularjs.org https://github.com/codeparty/derby/wiki/Community…

You use this argument a lot, but the ranter suggests that the reason many turn to Backbone is because of a self-selecting bias of it being the most popular.

there is something to be said about flocking to a framework purely based on popularity, Rails is a great example of that too, you sure as hell don't need it for most projects but there are a lot of developers familiar with it, whether it's good or not is another thing