Comparative analysis of 12 commonly used MVC frameworks in JavaScript_javascript skills

This article details 12 commonly used MVC frameworks in JavaScript. Share it with everyone for your reference, the details are as follows:

Gordon L. Hempton is a Seattle-based hacker and designer who spent months researching and comparing 12 popular JavaScript MVC frameworks and summarized each in his blog The advantages and disadvantages of each framework, the final result is that Ember.js wins.

There are four characteristic standards for this comparison, namely:

① UI Bindings
②Composed Views
③ Web Presentation Layer
④ Plays Nicely with Others

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

1. Backbone.js - Advantages: strong community, strong momentum; Disadvantages: weak abstraction, many functions need to be added urgently.

2. SproutCore - Advantages: Support for binding, reliable community, large number of features; Disadvantages: Over-specification, difficult to decouple from unnecessary features.

3. Sammy.js - Advantages: easy to learn and easier to integrate with existing server applications; disadvantages: too simple to be used in 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 Clogging occurs and the foundation is defective.

5. Cappuccino - Advantages: Large and well-thought-out framework, good community, great inheritance model; Disadvantages: Created by iOS developers, using JavaScript to simulate Objective-C.

6. Knockout.js - Advantages: Support for binding, complete documentation and tutorials; Disadvantages: Poor binding syntax, lack of unified view component hierarchy.

7. Javascript MVC - Advantages: reliable community; disadvantages: poor string-based inheritance model, too close relationship between controller and view and lack of binding.

8. GWT (Google Web Toolkit) - Advantages: comprehensive framework, good community, reliable Java-based component inheritance model; Disadvantages: may not withstand the test of time, in addition, Java The abstraction on the client side is a bit clumsy.

9. Google Closure - Advantages: Very good component-based UI composition system. Disadvantages: Lack of UI binding support.

10. Ember.js - Advantages: Very rich template system, with composite views and UI binding; Disadvantages: Relatively new, documentation is not complete enough.

11. Angular.js - Advantages: It has good considerations for template scope and controller design, has a dependency injection system, and supports rich UI binding syntax. Disadvantages: The modularity of the code is not strong, and the modularity of the view is not enough.

12. Batman.js - Advantages: clear code, simple binding and persistence methods; disadvantages: singleton controller is used.

After comparing the features of the above various Javascript MVC frameworks, Gordon believed that only Ember.js could fully meet his requirements, thus becoming the framework he finally chose.

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

I hope this article will be helpful to everyone in JavaScript programming.