Why is Backbone.js a bad option in the Technology radar 2012 of thoughtworks?
Posted
by
Cfontes
on Programmers
See other posts from Programmers
or by Cfontes
Published on 2012-12-05T16:51:25Z
Indexed on
2012/12/05
17:25 UTC
Read the original article
Hit count: 261
JavaScript
In the latest Technology Radar 2012 they state that Backbone.js has pushed to far on it's MVC abstraction and say that Knockout.js or Angular.js should be used instead.
I cannot get why they think that Backbone.js model is bad, for me it's just a way to create a standard so people can have some kind of roadmap to dev frontend JS without Spaghetti code.
Also for me Angular and Knockout solve a different problem, I like both of them but having to code all MVC classes is something I think is kind of a rework.
The thing is simple easy extendable and fast to learn, comes with a lot of goodies and is easy to combine with other Frameworks. (see Knockback.js)
Can anybody tell me what made it so bad to their eyes ?
© Programmers or respective owner