Yehuda Katz and Tom Dale (Tilde Inc.) interviewed at Fluent 2014
summary
Argues framework wars are overstated and shows why Ember trades flexibility for productivity by baking conventions into a larger codebase: Ember bakes in routing and conventions, router is the heart and soul, and that extra code prevents broken back/forward and refresh behavior in large SPAs. Claims ~70–90% of web apps share the same flow so opinionated defaults save time on trivial choices. Cites real deployments (Vine, NBC, Yahoo), ecosystem tools (Ember Inspector, promise work) and that it scales better for teams.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:02What is the benefit of having a framework
- 3:10What is the difference between Ember and Angular
- 6:26Why is the Ember Router important
- 9:16Why developers love trivial choices
- 13:01Embers community
- 15:52Promises
- 18:09Tools
related talks
59mEmber.js, and why the framework helps you unlocking unprecedented productivity.
40mSurprise Talk
08mInterview with Matt Creager
15mBirds-Eye Vue of Ember
46mArt and Science of Shipping Single Page Apps with Ember.js
31mTaming the Beast: Managing a really ambitious codebase
36mPanel: Ember at Scale
46mA Round Table on The State of Front-End: (Ember, Angular, React)