MDV is a Javascript shim which partially implements a design for HTML that supports a sensible dynamic separation between page display and the data which drives it.

MDV aims to get HTML to provide the essential foundation underlying most templating libraries. Further, it aims to allow dynamic web applications to declare the relationship between their data and presentation: updates to application data are reflected in the presentation and user input is assigned to application data.

In every platform that’s truly a platform it’s important to have a stable conceptual model of what’s “down there”. For Java that’s not the language, it’s the JVM. For the web…well…um. Yes, it bottoms out at C/C++, but that’s mostly observable through spooky action at a distance.

Can't say I agree with all of the stuff in it, but Chaplin is a neat take on a Backbone.js++</blockuote>
To investigate: how they handle composite/nested views.

While innerHTML used to be much faster than JS DOM methods, this no longer holds for modern browsers. Let’s have a look at a benchmark: http://jsperf.com/innerhtml-or-dom/4

In my experience writing Backbone apps, views are very primitive and tend to cause issues. There's no support for any sort of view nesting, which is totally critical for large applications with complex UIs. In contrast, Ember provides an easy way of nesting views inside one another.

The other thing you'll notice with Backbone is that there's a lot of micro-management required when building Backbone views. They need to be properly cleaned up by hand, otherwise you end up with zombie views bound to events, or events that don't fire at all.

Unlike most MVC-style configurations, Passive View results in no dependencies between view and model.

Upon further study and reflection, I decided that pattern that was here under the name "Model View Presenter" needed to be split, so I have separated it into Supervising Controller and Passive View.

Presenter First is a software development approach that combines the ideas of the model–view–presenter (MVP) design pattern, test-driven development, and Feature-driven development.

Presenter First concentrates on transforming each of a customer's requirements into a well tested, working feature as quickly and with as much correlation to the customer's story language (requirement) as possible. The language of the story or requirement is used to directly guide development of the feature – even naming the modules and function calls. As a consequence, the feature implementation tends to closely represent the customer's desire with little extraneous or unneeded functionality. The language of the source code also corresponds closely to the customer's stories.