jenweber

Be loud and be ready - my hopes for Ember.js in 2018

In 2018, I want to see Ember grow. But how could that be done in a strategic way? In this article, I'll take stock of our current resources and suggest how we could focus our efforts.

Sometimes when I am not sure how to achieve a goal, I imagine my future, successful self. I imagine that the goal has been achieved, using the same resources I have today, and I work backwards. What would I guess that those successful people of Future-Ember did?

1. The people of Future-Ember worked to increase public awareness so that more developers knew about it and considered it for their projects. The Core Team led by example, writing and speaking, and the rest of the community was empowered to do the same.
2. Future-Ember provided approachable, current, convincing materials for new visitors.

They were LOUD, and they were ready for the moment that they were heard.

jenweber

import Ember from 'ember';

export default Ember.Controller.extend({
  appName: 'Ember Twiddle'
});

jenweber

import Ember from 'ember';

export default Ember.Component.extend({
});

jenweber

import Ember from 'ember';
// in Ember 3.x, you would use import Controller from '@ember/controller';

export default Ember.Controller.extend({
// in Ember 3.x, use export default Controller.extend({
  
  blogPostTopic: '',
  queryParams: [{
    blogPostTopic: {
      type: 'string',

jenweber

import Ember from 'ember';

let RowItem = Ember.Object.extend({
	order: 0
});

export default Ember.Controller.extend({
  appName: 'Ember Twiddle',
  sortDirection: '',
  items: Ember.computed(function(){

jenweber

DRAFT needs review for accuracy

Is module unification something you can use today in an app? It seems like a lot of the discussion revolves around usage in addons, corner cases, or require using canary versions of Ember.

Yes, Module Unification is something that is currently available through a feature flag, which means that you can try it out today! Feature flags are the way that experimental features are tested in Ember, so use it in production at your own risk, and be aware that its behavior may change before it becomes part of default Ember. Learn more here about the currently available feature flags and how to use them in general.

Module Unification was proposed in RFC 143, and it was a common theme in Roadmap articles. Although there's a lot to it, some of the most visible benefits are a file structure overhaul and namespaced addons. The new file s

jenweber

import Ember from 'ember';

export default Ember.Component.extend({
});

jenweber

import Ember from 'ember';

export default Ember.Controller.extend({
  appName: 'Ember Twiddle'
});

jenweber

import Ember from 'ember';

export default Ember.Component.extend({
});

jenweber

import Ember from 'ember';

export default Ember.Component.extend({
});