3 ms·
Sorry you guys had trouble with Ember Data. Our first conception of Ember Data was that it would act as an ORM on top of JSON, and the architecture would allow
by tomdale 13y ago
Sorry you guys had trouble with Ember Data. Our first conception of Ember Data was that it would act as an ORM on top of JSON, and the architecture would allow developers to build adapters for many different kinds of backends.
Unfortunately, there is no JSON analog to SQL. Every existing backend forms their JSON differently, especially when you start modeling relationships. It would be like trying to build ActiveRecord if every team rolled their own query language for each new project.
We're trying to make this better in the long-term with projects like http://jsonapi.org http://jsonapi.org, and https://github.com/rails-api/active_model_serializers https://github.com/rails-api/active_model_serializers for Rails. We'll get there someday.
In the meantime, we totally rebooted the Ember Data project to make it simple for people to customize how their apps consume JSON APIs. Most people we've talked to have been very happy about the fact that the defaults are simple to override now, and how much simpler the internals have become. We have a small amount of work left to do before we declare a 1.0 final; in the meantime, we've cut a 1.0 beta build that you can get from http://emberjs.com/builds http://emberjs.com/builds.
- HNJohnC 13y agoSurely you guys know that the single largest barrier to using Ember is Ember-data right? I thoroughly tested all the available frameworks this summer and I was leaning heavily towards Ember until I tried actually using it with Ember-data and it was very ugly. I looked online and there was near universal condemnation of it from what I could find. Even Discourse didn't use it! I saw this link and thought "I bet they are announcing a completely new and working ember-data" and was surprised to see it wasn't even a topic in there. Ember-data drove me directly into the arms of Angular and I haven't looked back. I am completely stunned it wasn't your number one priority a long time ago.
- tomdale 13y agoI will challenge your assertion that it wasn't our number one priority. :) See http://emberjs.com/blog/2013/05/03/ember-data-progress-update.html http://emberjs.com/blog/2013/05/03/ember-data-progress-updat... for the blog post that did what you requested. We've probably fixed most of the issues you hit. You should give us another try!
- HNJohnC 13y agoOld news unfortunately; I'm specifically speaking of Ember data from July / August 2013 era. It was purportedly worse before that, I don't know because I only looked at it this summer. I understand many people don't write data centric apps and they full well find they don't need Ember-data or need a very sophisticated Ember-data but try to do anything of substance data wise and it's a nightmare.
- iamstef 13y agoI am glad angular (which has no data-layer) satisfies your needs :)
- zwily 13y agoI was thinking the same thing... Ember works great without ember-data. In fact, I haven't used ember-data in any of my 6 ember apps.
- iamstef 13y agoYa, I use ember-data when its appropriate, and not when its not.
- HNJohnC 13y agoWell, I guess there is the experience of those of us in the trenches actually working with these frameworks and large data centric applications and then there are people who want to argue semantics.