Rubbing it out

Ember.js 2.0 is all about removing stuff

Natali Vlatko
Eraser image via Shutterstock

The new Ember.js 2.0 drop is all about removing features that were deprecated from version 1.13. However, the gang behind the open-source JavaScript application framework want to make sure they’re really good at removing things.

The latest shipment from the team behind Ember.js have released version 2.0 with one distinct theme: removal. Yehuda Katz and Matthew Beale have described 2.0 as “not a traditional major release” with their focus firmly on removing deprecated features from version 1.13.

You can count on the following statement to be your main takeaway from this release:

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.

Katz and Beale have highlighted that major releases of libraries usually try and introduce new APIs or remove deprecated ones, with Ember.js 2.0 focusing on the latter. “Instead of introducing new features, the goal of Ember 2.0 is to remove accumulated cruft”.

SEE ALSO: Ember.js 1.13.0 out now

To stick to their commitment of giving every Ember codebase a path into 2.x, every deprecation from the 1.x series has been flagged. Since there’s no new features to flag or adopt for users, you’ll have to wait for future 2.x releases to get your hands on the new stuff.

The removed APIs

This “garbage collection” release features the removal of the following APIs:

  • Views have been removed and are replaced by Components, which fulfil the intended use-cases. Components are said to provide better isolation and scoping semantics.
  • The use-cases for Controllers have largely been eliminated.
  • ReduceComputed and ArrayComputed have been made obsolete by the Glimmer rendering engine introduced in Ember 1.13.
  • Context shifting in templates ({{#each}} and {{#with}} without block params) is removed from 2.0 onwards.
  • Legacy Handlebars helpers are removed in favor of the Ember.Helper API.

On top of all that, IE8 support has been ditched in favour of IE9+ support. For the 2.x series, the team want to concentrate on alignment with JavaScript, JavaScript modules, Ember Data (which is now a stable part of 2.0) and better stabilization and integration for the ecosystem.

Guides for 2.0 are up and ready on the website. If you’re looking for more information about the removal process, the changelog is the place to go.

Natali Vlatko
An Australian who calls Berlin home, via a two year love affair with Singapore. Natali was an Editorial Assistant for (S&S Media Group).

Inline Feedbacks
View all comments