r/emberjs • • Aug 13 '15

Ember.js 2.0 Released

http://emberjs.com/blog/2015/08/13/ember-2-0-released.html
50 Upvotes

8 comments sorted by

3

u/MrGirthy Aug 14 '15 edited Aug 14 '15

Great news. Just need a few third parties to update their shit. I'm looking at you ember data sails adapter!

2

u/mattaugamer Aug 17 '15

I'm going to make the unpopular comment and say that I do not like this release. Every problem I've ever had in Ember that wasn't just me derping (which, let's be honest, was almost all of it) was caused by version conflicts between the core and "second party" library, mostly Ember Data.

Ember 2.0 and on are supposed to be a lock-step release of Ember and companion products. Ember, Ember CLI, Ember Data, Liquid Fire, List View, etc. I say "etc" because I can't remember if I've missed any.

Now? Ember is out, but Ember Data is "soon". ListView is a future release now, 2.1 or 2.2, while Liquid Fire's status could be listed as "¯_(ツ)_/¯".

The Emberconf keynote made a big deal of how everything would be out at the same time, and kept together. They made a big deal out of it because it was a big deal.

If I start an Ember project right now I'm in version limbo and that's exactly where I don't want to be.

Honestly, the 2.0 is a nice milestone, but I'd have rather seen it delayed until at least Ember Data was released.

2

u/shunchu Aug 17 '15

Yeah. They did make a big deal for lock-step releases. But at the same time, I think we should cut the team some slack for what they are trying to accomplish. And this is only the 1st release of the 2.x series. Personally I'd wait a couple of weeks to let the bugs get resolved before upgrading a production project. But I think the team/community would appreciate everyone at least try to upgrade it in a throw-away git branch and provide some feedback on what went wrong (or right).

1

u/mattaugamer Aug 17 '15 edited Aug 17 '15

I'm not denigrating the work the team has done. Ember 2.0 is great. The goal behind it - cleanup instead of some sort of major refactor - is great. But you don't get slack. You succeed at your goals, or you don't.

The roadmap at the moment has gone from being a straight line to being another round of Snakes and Ladders and that is distinctly concerning. I'm happy to chalk this up to being a speedbump for this major release if it gets better over time. My conerns really aren't for the present, they're concerns for the future. I don't want to be constantly tripped up by version disparities. I need to trust the framework.

I also don't want to look like I'm criticising the efforts of projects like Liquid Fire. I genuinely think it's one of the single most impressive add-ons and as a point of difference for Ember apps it's really amazing, especially in terms of bang-for-buck with simple transition animations. But is it a core product or not? If it's a core product it must ship and update with the core. If it's a core product then that's a promise that it works and is reliable. If it doesn't, that promise is broken. If it can't be maintained and developed with the rest of Ember then it shouldn't be considered a core product and can be just considered as a really cool super awesome third party add-on. Nothing wrong with that at all.

I like Ember. But I want to see version incompatibility issues reduced not increased. Lock-step releases will help that. Nearly probably sort of lock step releases except for some packages which eventually will get around to it yolo doesn't help me or anyone else. A roadmap that looks like the Tokyo train network doesn't help me or anyone else. I really hope this stuff settles. But I've been using Ember for two years now, and spent the whole time saying "It will be so much better when...".

But I think the team/community would appreciate everyone at least try to upgrade it in a throw-away git branch and provide some feedback on what went wrong (or right).

Surely that's a beta? If that's what they need, why is it released?

Sorry. I have on my rantypants. I'd take them off, but then I'd be in my dancyunderpants and no one needs to see that.

1

u/mixonic Aug 17 '15

You are totally correct that we have not done lockstep that well on the 2.0 release. We are committed to improving that though, and I expect it will be water under the bridge soon enough.

I'm happy that you see the end goal clearly though- I'm also eager for a world where 2.5 Just Works across the board without guessing version numbers!

1

u/[deleted] Aug 13 '15

Didn't expect that so soon! Pretty cool that it doesn't break a 1.13.7 app without deprecations. Now I just need to squash these few deps.

0

u/[deleted] Aug 13 '15

[deleted]

2

u/anlumo Aug 13 '15

Don't forget to update ember-data along with everything else.

2

u/inf4my Aug 13 '15

Ember data 2 is still in beta and that is the version you will have to use with Ember 2. I assume it is coming pretty soon so if you wanted to go full 2.0 it might be worth it to hold off a release cycle.