[jenius]

Other than Ember Data, it seems like all the pieces here are things that marionette has. I was super interested to read this, swinging more towards marionette myself, just to get a perspective on what convinced you to change. But there really wasn't much comparion, it seemed to just be you going over the features of ember.

If you don't mind answering here, what made you go so strongly with ember over marionette?

[fleon]

One of the major factors in the debate was community support. Marionette is built on top of Backbone, which meant depending on support of two separate projects. Ember.js, on the other hand is by a single developer. Kind of like why people prefer buying Nexus phones. They are the first ones to officially get updated with the latest Android version. Others might take months before the handset manufacturer decides to update them.

Also, we were certain that we needed view hierarchies, and Marionette provided them too. Back in the day though, it was still in its early stages, and we couldn't really count on it. "What if an API change broke our app with the next upgrade?" we thought. Ember.js on the other hand was pretty much frozen and as in a 1.0 pre2 version. Also, there were many options available, Backbone+Marionette or Backbone+Thorax? It was confusing.