Plus poll results: Is Ember still relevant?

Ember 3.8 brings a couple of new features and some important fixes

© Shutterstock / Vikojam

The new release of the Ember project arrives with a couple of interesting new features and some important updates. In this article, we take a closer look at what’s new in Ember 3.8 and we present the results of our previous poll on the discussion around Ember and if it is a relevant tool in the JavaScript ecosystem. 

Ember is back with a new release.

Ember 3.8 signals the start of the 3.8 beta cycle for all sub-projects.

For those of you who are not familiar with it, the Ember project is a bundle that consists of:

  • Ember.js: The core framework for building ambitious web applications
  • Ember Data: The official data persistence library for Ember.js applications
  • Ember CLI: The command line interface for managing and packaging Ember.js applications

Let’s have a look at the most interesting highlights.

What’s more, at the end of the article we will dissect the results of our previous poll on the discussion around Ember and if it is [still] a relevant tool in the JavaScript ecosystem.

The updates

Ember.js – 3.8 brings a couple of new features and several important deprecations.


  • Element Modifier Manager: An object that is responsible for coordinating the lifecycle events that occurs when invoking, installing and updating an element modifier. This new feature is introduced as a very low-level API.
  • Array helper: Introducing the {{array}} helper to create an array in a template. This helper works in similar fashion to the already existing {{hash}} helper. The helper would be invoked as {{array arg1 ... argN}} and return the value [arg1, ..., argN].


  • Computed Property Overridability
  • Computed Property .property() Modifier
  • Computed Property Volatility
  • Deprecate @ember/object#aliasMethod
  • Component Manager Factory Function

Ember Data – This release does not bring any new features or deprecations to Ember Data but there are a couple of fixes. Check them out here.

Ember CLI – 3.8 doesn’t feature any new additions or deprecations to the CLI but there are some changes you should know about.

  • documentation: more links to the contributing guide were added, so users can more easily find out how to contribute
  • {{content-for}} was updated to allow the use of this on the same line if different types are specified (i.e., {{content-for 'head'}} {{content-for 'head-footer'}})
  • gitignore was updated to ignore Yarn .pnp files
  • the tests directory will be ignored when tests are turned off

For upgrading Ember CLI you simply use the ember-cli-update project:

npm install -g ember-cli-update

SEE ALSO: Angular, Ember, and Vue: Is choosing a framework simply a matter of taste?

Poll results – Ember is still very much relevant

Some months ago, V. Lascik wrote a blog post and took a hard look at Ember’s status in 2018, criticized its shortcomings and offered some points of potential improvements. One of his main points was that Ember is indeed a great framework, however, “without enough convincing reasons for the larger world to start to get it as well, it won’t matter.”

In our previous article covering the release of Ember 3.7, we revisited this discussion and we introduced a mini survey to find out what’s your opinion on this discussion and the results are in!

As you can see in the figures above, the vast majority of the respondents use Ember as their primary framework and they believe that Ember is still a very relevant tool in the JavaScript ecosystem.

Eirini-Eleni Papadopoulou
Eirini-Eleni Papadopoulou was the editor for Coming from an academic background in East Asian Studies, she decided that it was time to go back to her high-school hobby that was computer science and she dived into the development world. Other hobbies include esports and League of Legends, although she never managed to escape elo hell (yet), and she is a guest writer/analyst for competitive LoL at TGH.

Inline Feedbacks
View all comments