Comparison Analysis of 12 common JavaScript MVC frameworks _ javascript skills

This article mainly introduces the comparison and analysis of 12 common JavaScript MVC frameworks, and analyzes the advantages and disadvantages of the common JavaScriptMVC frameworks in 12 from a unique perspective, which has some reference value, if you need it, you can refer to this article to detail 12 common JavaScript MVC frameworks. We will share this with you for your reference. The details are as follows:

Gordon L. hemton is a hacker and designer in Seattle. He spent several months researching and comparing 12 popular JavaScript MVC frameworks, and summarized the advantages and disadvantages of each framework in his blog, the final result is: Ember. js wins.

The comparison involves four feature standards:

① UI Bindings)
② Composed Views)
③ Web Presentation Layer)
④ Good collaboration with other frameworks (Plays Nicely with Others)

For various JavaScript MVC frameworks, Gordon summarizes the advantages and disadvantages:

1. Backbone. js-advantages: a strong community, strong momentum; disadvantages: weak abstraction, many functions need to be increased.

2. SproutCore-advantages: Support for binding, reliable communities, and a large number of features; disadvantages: over-standardization, difficult to decouple from unwanted features.

3. Sammy. js-advantages: easy to learn, easier to integrate with existing server applications; disadvantages: too simple to be applied to large applications.

4. spine. js-advantages: lightweight, complete documentation; disadvantages: its core concept "spine" is an Asynchronous User interface, which means that the ideal user interface will never be congested, this foundation is flawed.

5. Cappuccino-advantages: large and well-thought-out frameworks, good communities, and great inheritance models. Disadvantages: created by iOS developers and simulated Objective-C using JavaScript.

6. Knockout. js-advantages: Support for binding, complete documents and tutorials; disadvantages: poor binding syntax and lack of a unified hierarchical relationship between view components.

7. Javascript MVC-advantages: reliable communities; disadvantages: the string-based inheritance model is poor, and the relationship between the Controller and the view is too dense and lack of binding.

8. GWT (Google Web Toolkit)-advantages: a comprehensive framework, a good community, and a reliable Java-based component inheritance model. Disadvantages: it may not be able to withstand the test of time. In addition, java's abstraction on the client is clumsy.

9. Google Closure-advantage: A component-based UI combination system. Disadvantage: lack of support for UI binding.

10. Ember. js-advantages: a rich template system with a composite view and UI binding; disadvantages: relatively new, incomplete documentation.

11. Angular. js-advantages: it has good considerations for the template scope and controller design, has a dependency injection system, and supports a wide range of UI binding syntaxes. Disadvantage: the code is not efficient, and the modular view is not enough.

12. Batman. js-advantages: the code is clear, and the binding and persistence methods are simple. Disadvantages: The Singleton controller is used.

After comparing the features of the various Javascript MVC frameworks, Gordon believes that only Ember. js can fully meet his requirements and become his final framework.

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

I hope this article will help you design JavaScript programs.