Keynote With Yehuda Katz and Tom Dale
summary
Argues that a framework should encode community best practices rather than just offer maximally flexible primitives, comparing Ember and Angular: Angular exposes dependency injection and directive APIs as a toolkit, Ember builds opinionated defaults—components with isolated scope and transclusion, a router is the heart and soul that converts URLs to models, built-in loading/error templates, and query-parameter mapping on Canary. Claims these choices reduce boilerplate, surface errors earlier, and let a shared vocabulary evolve useful higher-level features.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:44Frameworks vs Libraries
- 2:54Dependency Injection
- 4:44Flexibility
- 6:18Observations
- 13:58Ember components
- 15:00Ember Router
- 15:52Angular
- 18:43Code Example
- 20:49Flexible API
- 21:30Frameworks
related talks
26mModern Javascript Frameworks - Introduction to Ember.JS and Ember-CLI
01h 00mEmber = Angular = React
59mEmber.js, and why the framework helps you unlocking unprecedented productivity.
40mSurprise Talk
40mFRONTEND CHOICES
12mInterview with Kyle Simpson
01h 28mComparing Hot JavaScript Frameworks: AngularJS, Ember.js and React.js
04mA model walks into a JavaScript framework