[2015-08-31 Mon] Major update: TodoMVC contains implementations using many different MV* frameworks.

A set of simple demos that get implemented in different frameworks for learning and comparison purpose.

• State “DONE” from “TODO” [2015-08-14 Fri 19:01]

Goal: Fully understand it, even the source code.

It's all too easy to create JavaScript applications that end up as tangled piles
of jQuery selectors and callbacks, all trying frantically to keep data in sync
between the HTML UI, your JavaScript logic, and the database on your server.

• [ ] Models should be able to be passed around throughout your app, and used anywhere that bit of data is needed.
• Models should be generally unaware of views.
• Backbone remains unopinionated about the process used to render View objects and their subviews into UI: you define how your models get translated into HTML (or SVG, or Canvas, or something even more exotic).

• Backbone’s Views are the equivalent of ‘controllers’ on MVC frameworks

• State “CANCELED” from “TODO” [2015-08-31 Mon 13:28]

[2015-08-31 Mon] Not very intuitive. Give up.

• Backbone.js enforces that communication to the server should be done entirely through a RESTful API. The web is currently trending such that all data/content will be exposed through an API.

A poorly written part, feels more like a list of APIs.

Very objective comparison with good information table.

• Backbone.js <-> Minimalism
• Ember.js <-> Pragmatism
• Angular.js <-> Innovative

Not updated for 2 yrs, but still a useful ref.

Note the <template> tag is NOT really recommended as it requires the content to be valid HTML as opposed to the text/template which browsers will simply ignore.