The future of this project

[epyx25]

I just want to know the status / future of this project. I see, after a big pause (5 months) there are finally some commits. I am seriously thinking about switching from ED because of the lack of relationship rollbacks.

• Is it compatible with Ember 2.3.upwards?
• I see it is a bower dependency. How does it work with ember cli project? Do you plan it to make an addon out of it. (I am asking it because of blueprints)
• Has @gordonkristan abandoned this project?
• Do you plan to make a documentation?

[deleter8]

• We have not verified 2.3, the last we've verified is ember 2, however we don't know it isn't - if this is the only thing holding you back (based on your other issue I can see some other potential concerns) we can check this for you.
• Ember-cli is on the roadmap, I can't promise any date though
• I will let @gordonkristan comment on his participation in the project
• A more thorough documentation than already exists is probably a ways off, however we will be responsive with questions that can't be answered by the existing documentation

[gordonkristan]

• The latest version I've tested it on was 2.1 Although I see no reason why it wouldn't work with 2.3+, as the Ember team is very serious about semantic versioning.
• That's something I wouldn't mind tackling, I just haven't found the need yet. I'll take a peak into what it will take (I can't imagine it'll be too hard).
• I haven't abandoned it, I just don't work on it much any more. That's partly due to my decreased free time, but mostly because I didn't think anybody was actually using it. If that's not the case, I'd be happy to throw some more time at it. 😄
• I've wanted to make better documentation for a while, but writing documentation is hard. If you have any specific requests for documentation that could be a good starting point for me.

As for switching from ED, it could be a good move depending on your situation. I can say, with reasonable certainty, that if you switched to EG and we all got hit by a bus that you would probably be able to figure out the internals yourself. There's a lot of code, but most of the code is for adapters and serializers. The core of Ember Graph is fairly simple to understand at a high level (even if there's some gotchas once you get down into some of the complicated logic). That's obvious not desired, and Ember Data has much better support, but you'll certainly never be "stuck" if you switched.

If you have any other questions feel free to ask. 😃

[epyx25]

@gordonkristan @deleter8 thanks for your answer. It is good to see, that you are still active. Ember Data has maybe better support, and more contributors, but this has a downside too:
It takes months (years?) to introduce a new feature (see rollback relationships) , EG's code is easier to look through.

We decided to finish our current project with ED, but the next one will start soon. If we do it with Ember (and not Angular) i will advocate for trying out EG.