Helping you select an MV* framework
Introduction
Developers these days are spoiled with choice when it comes to selecting an MV* framework for structuring and organizing their JavaScript web apps.
Backbone, Ember, AngularJS, Spine... the list of new and stable solutions continues to grow, but just how do you decide on which to use in a sea of so many options?
To help solve this problem, we created TodoMVC - a project which offers the same Todo application implemented using MV* concepts in most of the popular JavaScript MV* frameworks of today.
JavaScript Apps
- Backbone.js
- AngularJS
- Ember.js
- KnockoutJS
- Dojo
- YUI
- Agility.js
- Knockback.js
- CanJS
- Maria
- cujo.js
- dermis
- Montage
- Ext.js
- Sammy.js
- Stapes
- Epitome
- soma.js
- DUEL
- Kendo UI
- PureMVC
- Olives
- PlastronJS
- Dijon
- rAppid.js
- Funnyface.js
- Knockout + ClassBinding
- AngularJS (optimized)
Compile To JavaScript
MVC Extension Frameworks
Module Loaders
- Backbone.js + RequireJS
- Ember.js + RequireJS
- Knockout + RequireJS
- AngularJS + RequireJS
- CanJS + RequireJS
- TroopJS
- Thorax + Lumbar
Real-time
Compare these to a non-framework implementation
* R = App also demonstrates routing
* Maroon = App requires further work to be spec-compliant
New in 1.1 - TBA
- We now have 18 stable apps and 36 in labs.
- Dart
- TypeScript + Backbone.js
- TypeScript + AngularJS
- Serenade.js
- CanJS + RequireJS
- Chaplin + Brunch
- Thorax + Lumbar
- Kendo UI
- CanJS replaced the JavaScriptMVC app
- Many app frameworks and libraries have been upgraded to the latest version
- XSS issues in several apps have been resolved
- The homepage got reorganized with new categories
- Various consistency fixes across all apps
Selecting a Framework
Once you've downloaded the latest release and played around with the apps, you'll want to decide on a specific framework to try out.
Study the syntax required for defining models, views and (where applicable) controllers and classes in the frameworks you're interested in and try your hand at editing the code to see how it feels using it first-hand.
Please ensure that if you're happy with this, you do spend more time investigating the framework (including reading the official docs, the source and its complete feature list). There's often a lot more to a framework than what we present in our examples.
Getting Involved
Is there a bug we haven't fixed or an MV* framework you feel would benefit from being included in TodoMVC?
If so, feel free to fork the repo, read our contribution guidelines, and submit a pull request — we'll be happy to review it for inclusion.
Make sure you use the template as a starting point and read the app specification.