Re:Why we're moving away from Ember.js
by coolsunglasses on Friday March 22, 2013 @04:09PM
(#5425346)
>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.
Re:Why we're moving away from Ember.js
by steveklabnik on Friday March 22, 2013 @04:25PM
(#5425449)
I'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?
Re:Why we're moving away from Ember.js
by coolsunglasses on Friday March 22, 2013 @05:45PM
(#5425996)
I'm not sure how Ember Data is different beyond providing a smarter interface to collections and models than BackBone.
Re:Why we're moving away from Ember.js
by steveklabnik on Friday March 22, 2013 @09:26PM
(#5426862)
Hence 'not ready yet.'
Have you actually read http://docs.angularjs.org/api/ng.$http or https://github.com/documentcloud/backbone/blob/master/backbo... ?
Re:Why we're moving away from Ember.js
by coolsunglasses on Friday March 22, 2013 @06:56PM
(#5426307)
Yes, I think we just disagree on how different and special Ember Data is.
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).