Road to Ember 2.0

Slides from my talk at Ember.BP meetup 2015 February

http://www.meetup.com/ember-bp/events/219828350/

Transcript

1. THE ROAD TO EMBER 2.0 @xeppelin github.com/zeppelin
2. Q: HOW MANY NEW FEATURES WILL EMBER 2.0 HAVE?
3. A: ZERO!
4. WTF?!?
5. FEATURES DEVELOPED ON MASTER BEHIND FEATURE FLAGS AND ROLLED OUT WHEN STABLE
6. Beta Release Canary
7. NO BIG-BANG REWRITE
8. 2.0 DOESN’T ADD NEW FEATURES, JUST REMOVES THE DEPRECATED ONES
9. STABILITY WITHOUT STAGNATION™
10. THANKS :)
11. NO, SERIOUSLY: FEATURES
12. #1- MORE INTUITIVE ATTRIBUTE BINDINGS
14. Transition plan We do not plan to remove support for existing templating syntax
 (or no-longer-necessary helpers like bind-attr) in Ember 2.0
15. #2 - IMPROVED COMPONENT SYNTAX
17. Transition plan We have no plans to remove support for the old component syntax
 in Ember 2.0
18. #3- BLOCK PARAMETERS
21. Transition plan Block parameters will hopefully land in 1.12, and at that point the two special forms for {{each}} and {{with}} will be deprecated.
 You should refactor your templates to use the new block parameters syntax once it lands, as it is a purely mechanical refactor.
22. #4- MORE CONSISTENT TEMPLATE SCOPE
24. Transition plan We plan to deprecate support for the context-shifting helpers in Ember 1.10 and remove support in Ember 2.0. This change should be entirely mechanical.
25. #5- ONE-WAY BINDINGS BY DEFAULT
27. Transition plan The new one-way default is triggered by the use of new component syntax. This means that component invocations in existing templates will continue to work without changes. To preserve the same semantics during a refactor to the new HTML- based syntax, you can simply mark all bindings as mut.
28. #6- SEPARATED COMPONENT PARAMS
32. Transition plan In Ember 2.0, we will stop setting attributes as properties
 on the component itself. We will also provide a transitional mixin that Ember addons can use that will make provided attributes available as attrs.*.
 This will allow add-ons to move to the new location, while maintaining support for older versions of Ember.
33. #7- ROUTABLE COMPONENTS + SERVICES
34. WORTH TO MENTION HERE: NO MORE MODEL PROXYING
36. TODAY’S CONTROLLER + VIEW =
 TOMORROW’S ROUTABLE COMPONENT
37. MOVE EXISTING CONTROLLER LOGIC INTO SERVICES
39. Transition plan We plan to land support for routable components in Ember 1.12, and deprecate routable controllers at the same time. We plan to remove support for routable controllers in Ember 2.0. We will also provide an optional plugin for Ember 2.0 apps that restores existing behavior. This plugin will be included in the Ember automated test suite to ensure that we do not introduce accidental regressions in future releases on the 2.x series.
40. #7- IMPROVED ACTIONS
46. Transition plan We will continue to support the sendAction API for the foreseeable future in today's Handlebars syntax.
47. SPEAKING OF REACT
48. #8 VIRTUAL DOM
49. In Ember 2.0, we will be adopting a "virtual DOM" and data flow model that embraces the best ideas from React and simplifies communication between components.
50. TOOLING
51. MANY NEW FEATURES WILL REQUIRE EMBER-CLI
54. USE EMBER-CLI TODAY!
55. 540+ ADDONS, AND COUNTING!
57. ONE MORE THING…
58. FASTBOOT™
59. EMBER RUNNING ON THE SERVER!
60. RENDERS THE APP ON THE SERVER,
 THEN WAKES UP FROM THAT STATE ON THE CLIENT
61. THANKS! https://github.com/emberjs/rfcs/pull/15
62. THANKS! (THIS TIME FOR REAL) @xeppelin github.com/zeppelin