Backbone and Ember (at least for some extent) are MVC frameworks that provide you with classes to extend to have certain functionality (events, validations, iterations over collections, bindings etc.).
Enyo seems to be more declarative framework for defining your UI components.
In fact, you most probably could combine two together (esp. taking the 13KB weight in account, makes it a really-lightweight thingie).
Comments
I was excited about this a while back, but with Backbone and Ember (Synapse, Handlebars, etc, too), I'm not so sure Enyo is that awesome anymore.
(I'm confused at the comments here lamenting the lack of a UI side of Enyo. I thought that UI elements were a decent part of Enyo?)
Backbone and Ember (at least for some extent) are MVC frameworks that provide you with classes to extend to have certain functionality (events, validations, iterations over collections, bindings etc.).
Enyo seems to be more declarative framework for defining your UI components.
In fact, you most probably could combine two together (esp. taking the 13KB weight in account, makes it a really-lightweight thingie).
Ember, unlike backbone, is a declarative framework for defining your UI components.
I was thinking of learning Backbone.js soon, and now I see this, can you elaborate a bit on the differences between Backbone and Enyo?