The Ember Times - Issue No. 46

හෙලෝ Emberistas!

Again you can enjoy reading The Ember Times in both the e-mail and the blog format to share it even better with your Ember friends.

This week we'll highlight a new RFC deprecating features from ancient Ember times and a sweet reminder for blogging about your best wishes for Ember and - last, but not least - we have a brand-new Readers' Question❓✨ for you!


Moar #EmberJS2018 blog posts wanted!

Original Tomster Mascot Image

We've already seen a lot of thoughtful blog posts from the Ember team's call for community blog posts. But we're hoping for more! Have something to say?

Write a blog post by May 30th to propose goals and direction for Ember in the remainder of 2018. The content of these posts will help the core team to draft their first Roadmap RFC.

Looking for inspiration? Check out the #EmberJS2018 hashtag on Twitter or @zinyado's repo collecting posts on GitHub.


Global resolution and more for Ember 🐹

@Gaurav0 has submitted an RFC to finally deprecate the Globals resolver and the related API. The Globals resolver is primarily a holdover from the early days of Ember when people used Ember without Ember CLI.

The API allowed the creation of an App global like this:

1
2
// app.js
var App = Ember.Application.create();

and the further setup of your Ember app based off this global:

1
2
3
4
5
6
7
8
9
10
// app.js
App.Router.map(function() {
  this.route('about');
});

App.AboutRoute = Ember.Route.extend({
  model: function() {
    return ['red', 'yellow', 'blue'];
  }
});

Using Ember CLI as the build tool for Ember apps has been recommended for years and is widely adopted in the community. Yet, if you're an active user of the Globals resolver API you should definitely give the original proposal for deprecating it a read and leave your thoughts on its use cases in the comments.

Furthermore, contributors to Ember this week worked on preventing memory leaks in tests (1, 2), nifty bug fixes (3, 4) and more internal and devops-driven improvements (5, 6, 7).


Get involved with the new Ember guides

The Learning Team has been working on a new and improved version of the Guides app. It's now made with Ember.js and is more shiny than ever. The Guides app is almost ready for a proper release, but before we do so, we would love for you to try it out. If you find any issues then please report them.

Or if you feel in a particulary good mood, look through existing issues in the Guides app or the Guides source and start contributing to the new guides.


Contributors' Corner

Many thanks to @rwjblue, @krisselden, @toddjordan, @kennethlarsen, @runspired, @ryanto, @nummi, @chancancode, @twokul, @kellyselden, @sivakumar-kailasam, @kategengler, @pzuraq, @dfreeman, @mansona and @Gaurav0 for contributing to Ember core projects this week. 💖


Readers’ Questions: “Why does Ember still use RSVP?”

Office Hours Tomster Mascot

This week's Readers’ Question revolves around Promises: Why does Ember ship with RSVP.Promise by default and why would it not rely on a regular Promise polyfill instead?

In his detailed write-up, Ember Core team member @ef4 will answer everything you need to know about the origin of RSVP in Ember, what it has been and still is used for and if Ember will be going all in regarding native Promises in the future. You can read the full answer on the offical Ember forum.

Submit your own short and sweet question under bit.ly/ask-ember-core. And don’t worry, there are no silly questions, we appreciate them all - promise! 🤞


That's another wrap! ✨

Be kind,

Gaurav Munjal, Edward Faulkner, Sivakumar Kailasam, Kenneth Larsen, Amy Lam, Jessica Jordan and the Learning Team


comments powered by Disqus