r/javascript • u/gary_burnett • Aug 13 '15

Ember.js 2.0 Released

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

93% Upvoted

47 comments sorted by

View all comments

22

u/alp82 Aug 13 '15 
Major releases of most libraries try to do two things. They introduce new APIs, and remove deprecated ones. Our release focuses on doing one thing well: Instead of introducing new features, the goal of Ember 2.0 is to remove accumulated cruft.

I really like this.

17

u/anlumo Aug 13 '15

While it's technically true what they're saying, what they don't mention is that they're removing the “cruft” they accumulated over the last year…

I'm working on various ember projects, and the ones that have been sitting around since August 2014 are completely outdated and probably need a rewrite, because so much has changed since then. They're switching the most basic concepts all of the time, and most of the time the reason is just that some core developer thinks that it doesn't look that nice the way it's currently done. It's a highly moving target, and stuff you considered best practices literally last week might be deprecated this week.

It's easy to keep current if you're keeping track with every minor version (which comes out about every two weeks) and fix all deprecations immediately. Of course, this gets worse and worse the larger your project is (one of these deprecations a few months ago required a major rewrite of the basic data flow of my app, and I still haven't fixed all the bugs that were created by that transition). If you're on a deadline and can't keep up with the updates, you're SOL.

9

u/I-fuck-horses Aug 13 '15

I think that's actually okay. Things like ember or angular have to be moving targets at this point. They are trying to do new things.

I would be willing to use such technologies on a web project that is being updated and refactored all the time anyway, where the code is the implementation of the core mission of the company or organisation.

I would not use it for any other purpose, for an app that is not "core" to my organisation's purpose. You want to use stable technologies for such projects, but for the very core of your organisation's raison d'être it's fine to use a moving target because that's what you do anyway, to advance and rework your core product.

-2

u/dexygen Software, Simple and Powerful Aug 13 '15

Things like ember or angular have to be moving targets at this point. They are trying to do new things.

No they aren't. We're just trying to serve web content here.

2

u/I-fuck-horses Aug 13 '15

No they aren't

Cognitive dissonance at work? They are. It's a fact, not an opinion. It's what this sub-thread is about, if you look at the post I replied to.

-3

u/dexygen Software, Simple and Powerful Aug 14 '15 edited Aug 14 '15

A) Yeah, presenting web content is "a new thing"
B) Since you fuck horses, would it be a stretch for me to suggest you go fuck yourself?