3 ms·
It's not like that. I'm saying use Angular, Ember, Knockout, whatever - just not Backbone. Unless you know Backbone is what's needed for your project, or you yo
by lefnire 14y ago
It's not like that. I'm saying use Angular, Ember, Knockout, whatever - just not Backbone. Unless you know Backbone is what's needed for your project, or you yourself really love Backbone. What I'm discouraging here is its popularity as the de-facto client MV*. I'm under the impression that most people today, when thinking about their next JS project, will use Backbone because it's the most popularly-touted framework where It shouldn't be. It's a great framework, and die-hards & specific projects should indeed use it. But the majority should use one of the other frameworks.
- ricardobeat 14y agoEmber, Knockout, Angular, Batman, all have data-binding in their core. Backbone doesn't. If you like writing client code where you have control over rendering and DOM manipulation, Backbone is the best choice short of building your own framework.
- joshontheweb 14y agoAgreed. Also backbone gives you the flexibility to use it on the backend or as the data models behind a canvas app or other kinds of non-html rendering.
- joshontheweb 14y agoProbably should have said that in your article if thats what you meant. It came off as a pretty insular point of view with 'rant' in the title.
- lefnire 14y agoUpdated the article, thanks for the advice