Birds-Eye Vue of Ember
summary
Claims that Vue knowledge maps directly to Ember Octane and v3 and that Ember favors convention over pick your own tools. Practical specifics include Ember CLI scaffolds components and tests, arguments use @ not declared props, state uses tracked + getters replace Vue computed and observers are discouraged. Examples of parity and gaps: modifiers and blocks mirror directives and slots while single file components and built in transitions are not present but addons like ember-css-transitions and ember-animated reproduce them. Generators produce tests and Ember Data and services handle shared state.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:47What is this talk about
- 2:04CLI
- 2:36Components
- 3:33Props
- 4:38Tracking State
- 5:49Native Events
- 7:02Views
- 7:30Blocks
- 8:46State
- 9:55Router
- 11:09Data
- 12:01Testing
- 12:34Transitions
- 13:50Resources
related talks
24mNew to Ember: What ARE All These Things?
29mIdiomatic Ember, Sweet Spot of Performance and Productivity
26mModern Javascript Frameworks - Introduction to Ember.JS and Ember-CLI
29mOctane: A Paradigm shift in EmberJS
21mYehuda Katz and Tom Dale (Tilde Inc.) interviewed at Fluent 2014
40mEmber's Technical Foundations – And How They Are Changing
58mOpening Keynote
34mComparing Patterns in React and Ember