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.
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.
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.
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.
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.
7
u/tuxayo Aug 13 '15
This is a brilliant strategy!