3 ms·
> Every major competitor to Ember (including its predecessor, SproutCore) has a data layer that does more than pass the buck off to jQuery SproutCore had a rob
by wycats 14y ago
> Every major competitor to Ember (including its predecessor, SproutCore) has a data layer that does more than pass the buck off to jQuery
SproutCore had a robust data layer, but 2013-era frameworks mostly expose HTTP directly as the abstraction to use, either via $.ajax or a framework-specific HTTP library. Other frameworks are not trying to solve data persistence and loading beyond delegating to HTTP, but Ember's solution isn't ready yet (so we don't get to say that it's a win of using Ember over the competition -- yet).
- coolsunglasses 14y ago>Other frameworks are not trying to solve data persistence and loading beyond delegating to HTTP I don't think that's true, given how Backbone and Angular are designed.
- steveklabnik 14y agoI'm not an expert in JS frameworks, but my understanding is that backbone converts 'save this model' to '{PUT,PATCH} /models/:id', and then makes the request. Isn't that just delegating to HTTP?
- coolsunglasses 14y agoI'm not sure how Ember Data is different beyond providing a smarter interface to collections and models than BackBone.
- steveklabnik 14y agoHence 'not ready yet.'
- jsg 14y agoHave you actually read http://docs.angularjs.org/api/ng.$http http://docs.angularjs.org/api/ng.$http or https://github.com/documentcloud/backbone/blob/master/backbone.js#L1110 https://github.com/documentcloud/backbone/blob/master/backbo... ?
- coolsunglasses 14y agoYes, I think we just disagree on how different and special Ember Data is.