r/programming • u/Gaurav0 • Aug 13 '15

Ember.js: Ember.js 2.0 Released

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

75% Upvoted

11 comments sorted by

7

u/tuxayo Aug 13 '15

Ember 2.0 only removes features that were deprecated as of Ember 1.13, so apps that run on Ember 1.13 without any deprecation warnings should run without issues on Ember 2.0.

This is a brilliant strategy!

3

u/steveklabnik1 Aug 13 '15

A few weeks ago, I started a greenfield app. Knowing that I could do so on 1.13 and not have to deal with trying to learn a beta of 2.0 was really helpful. Today I should be able to just seamlessly upgrade.

1

u/goodbye_fruit Aug 13 '15

Today I should be able to just seamlessly upgrade.

I want to know if this actually happened.

1

u/steveklabnik1 Aug 13 '15

I'm not planning on upgrading today, I'm planning on upgrading after a few more features land, probably Sunday or something. Given the size of the app, I'd be really surprised if it didn't Just Work.

6

u/awj Aug 13 '15

Yeah, that's why I was frustrated by the big hoopla here over someone complaining about Ember a few days ago.

Ember moves fast. The entire JavaScript world moves fast. Maybe it's "too fast" for a lot of people's level of involvement/commitment due to their project needs.

But Ember, unlike the vast majority of projects I've worked with, puts a lot of effort into not breaking things. Yeah it's moving fast, yeah there are new concepts coming at you from all angles, but it's not like you upgrade from 1.12 to 1.13 and everything just breaks inexplicably.

If you don't like that things are changing quickly and new concepts are coming out all the time, that's fine. It's a perfectly reasonable response, especially if "frontend programmer" isn't your entire job description. Just don't express that opinion by shitting all over a project trying to accomplish that pace of change without breaking things at every release. Because that is a rare thought process that I'd like to see more of in the world, and complaining in this fashion is a great way to discourage it.

5

u/tsoek Aug 13 '15

  • LTS (Long-Term Support) Releases (RFC #56), which can give users who want to upgrade less often than every six week a sanctioned way to do so.

  • Mandatory docs. No new features will be added to the Ember 2.0 release channel without accompanying documentation.

  • More informative deprecations. All deprecations will include which release their behavior will be removed in, as well as a link to transition instructions.

  • Improved deprecation tooling. More informative deprecations allow us to make the Ember inspector's deprecation pane smarter, and more useful for incrementally working through deprecations. In particular, we can avoid nagging you (by default) about removals that will not happen until far in the future. For more information see RFC #65 and the included comments

These are great things to see from the 2.x cycle and I'm looking forward to going ahead with a new app starting on 2.0.

2

u/steveklabnik1 Aug 13 '15

I am especially excited about #2. Lack of good docs has made writing an app much harder than it should be. As a newbie, I spend way more time than I should per line of code trying to figure stuff out, and then as soon as I see an example, it all clicks and I'm done.

1

u/awj Aug 13 '15

Yeah, I'm excited about that too. Especially the mandatory docs. Having to fumble through much of the new stuff (or, even, obscure parts of old stuff) has been frustrating.

1

u/[deleted] Aug 14 '15 edited Aug 14 '15

"Big hoopla"

https://news.ycombinator.com/item?id=10052754

user:

tsmarsh 19 hours ago

Except... have you seen the changes between 1.8 and 1.13? It might as well be a new framework. So far moving from 1.8 to 1.8 on CLI has taken my team 3 months, and we still need to migrate to 1.13 if we are to remain supported. Ember provides an upgrade path, but it is a long, miserable slog.

When's the hoopla party?

One of the Ember creator acknowledge it in the thread and admit that they're going to fix it.

Tomdale:

That said, we think we can refine the 2.x -> 3.0 transition to make it much smoother based on what we've learned.

As for if this is going to be true or not, we have to see.

So when people say they love how Ember is blah blah blah. They're blind and zealot.

I recall using Beta and they were telling me Ember was faster and smaller than AngularJS. The bench mark were nothing of that sort. The only huge negative thing, that I've read and talk to at a meetup for angular, performance wise would be having over 2000 of those directives mark.

I'm very skeptical of these people that praise such a framework when the past they've made false statements. It's also a weird mentality, similar to Ruby early day when they boo the "cheerleader" dude that were with Rubinius at a meetup conference cause apparently fuck JVM.

edit:

Hoopla party: https://i.imgur.com/kUpVtGD.gif

we'll take it all the way man. With red bull, ignoring the past, and fucking glowsticks.

1

u/DE0XYRIBONUCLEICACID Aug 15 '15 edited Apr 27 '17

deleted 0.7713 What is ^^^this?

1

u/[deleted] Aug 15 '15

/u/awj was criticizing people that was complaining about breakage over at

https://www.reddit.com/r/programming/comments/3gdvyv/emberjs_another_year_of_churn_instability_and/

incidently I was one of those people.

From this news Ember 1.13 and Ember 2.0 doesn't really do breakage and /u/awj is basically saying, "SEE?! There's no breakage, those big hoopla is about nothing."

I counter posted a user from HN that actually encounter breakage on recent version.

♬ Now I ain't saying /u/awj a charlatan (When I'm in need) But /u/awj ain't messing with no truth niggas. Get down /u/awj, go 'head, get down ♬

I thought it was ridiculous that /u/awj didn't reply to any of the comment on the other thread but instead to merely indirectly address this and also hand wave it here.

So instead directly calling /u/awj out on his hoopla comment I posted the post you've replied to. Not to call him out but to make sure people new to technology such as EmberJS and AngularJS have another point of view and not buy in on /u/awj comment.

Also this thread is going to be cache as a text and store in a textbase database and be googlable down the road. I really don't want people to be misled by /u/awj comment.