Why we're moving away from Ember.js

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.

[ Parent | on HN ]

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?

[ Parent | on HN ]

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.

[ Parent | on HN ]

Re:Why we're moving away from Ember.js by steveklabnik on Friday March 22, 2013 @09:26PM (#5426862)

Hence 'not ready yet.'

[ Parent | on HN ]

Re:Why we're moving away from Ember.js by jsg on Friday March 22, 2013 @06:17PM (#5426139)

Have you actually read http://docs.angularjs.org/api/ng.$http or https://github.com/documentcloud/backbone/blob/master/backbo... ?

[ Parent | on HN ]

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.

[ Parent | on HN ]