Choosing a JavaScript MVC Framework

Another good resource for choosing a framework is TodoMVC (http://todomvc.com/). It doesn't give you the philosophy and history behind each framework, but it does show you an end-to-end example (however constrained) of what it's like to use the framework in day-to-day work.

As a developer, deciding on a [framework|library|language] is one of my least favorite things to do. Naturally I want to make the right long-term decision based on my idiosyncratic needs, which results in countless hours of research, so I really appreciate posts like these. Huge time saver.

As an aside, some have argued (see previous Angular / Ember deck posted to HN) that Angular is something for building frameworks rather than a framework itself. I would also say that the documentation for Angular is comprehensive but not good (as a newbie). With the version change to 1.2 a number of issues crop up that invalidate old solutions like $sce content escaping and other bindings, and often times the documentation on the AngularJS site goes a bit beyond comprehension that have yet to pass the appropriate "abstracto-cline" of understanding.

Thanks again for the analysis - well done.