[to] Comparison of 12 JavaScript MVC frameworks

from:http://www.infoq.com/cn/news/2012/05/js-mvc-framework/

Gordon L. Hempton, a Seattle hacker and designer, spent months researching and comparing 12 popular JavaScript MVC frameworks and summarizing the pros and cons of each framework in the blog, and the end result is that Ember.js wins.

The comparison of the characteristics of the standard has four kinds, namely:

• UI bindings (UI Bindings)
• Composite view (composed views)
• Web presentation layer (Web Presentation layer)
• Good collaboration with other frameworks (Plays nicely with Others)

For various JavaScript MVC frameworks, Gordon summarizes the pros and cons:

2. backbone.js--Advantages: Strong community, strong momentum; disadvantage: abstract weak, many functions need to increase.
4. sproutcore--Advantages: Support for bindings, reliable communities, lots of features, Cons: Over-spec, difficult to decouple from unwanted features.
6. sammy.js--Advantages: Easy to learn, easier to integrate with existing service-side applications, disadvantages: too simple to apply to large applications.
8. spine.js--Advantages: Lightweight, documentation is complete; disadvantage: Its core concept "Spine" is the asynchronous user interface, which means that the ideal user interface will never clog, and this foundation is flawed.
10. cappuccino--Advantages: Large, well-thought-out framework, good community, great inheritance model; Cons: Created by iOS developers, use JavaScript to emulate objective-c.
12. knockout.js--Advantages: Support for bindings, complete documentation and tutorials; Cons: Poor binding syntax, lack of a unified view component hierarchy.
14. Javascript mvc--Advantages: a reliable community; disadvantage: The string-based inheritance model is poor, the controller is too dense with the view and lacks the binding.
16. GWT (Google Web Toolkit)-Advantages: A comprehensive framework, a good community, a reliable Java-based component inheritance model, a disadvantage: you may not be able to withstand the test of time, in addition, Java on the client's abstraction is somewhat clumsy.
18. Google closure--Benefits: A good component-based UI composition system. Disadvantage: Lack of UI binding support.
20. ember.js--advantages: A rich template system with composite views and UI bindings; Cons: Relatively new, incomplete documentation.
22. angular.js--Advantages: The template range and controller design are well considered, have a dependency injection system, support rich UI binding syntax. Disadvantage: The code is not strong in modularity, and the view is not modular enough.
24. batman.js--Advantages: The code is clear, binding, persistent method is simple; disadvantage: A single controller is used.

After a comparison of the various JavaScript MVC framework features, Gordon believes that only Ember.js can fully meet his requirements, thus becoming his final choice of framework.

Have you ever used some JavaScript MVC frameworks? Welcome to participate in the discussion.

[to] Comparison of 12 JavaScript MVC frameworks