Q&A with Ed Faulkner
summary
Plans target a router rewrite built on tracked reactivity and lifetime primitives so routes drop bespoke hooks like beforeModel/activate and support stateful live connections natively, with an incremental migration path that lets new routes opt in. V/Vite integration with Embroider is nearly done but blocked by V’s multi-stage preoptimization quirks and addons that use AMD or custom Broccoli transforms. Embroider already yields much smaller production bundles and promises sub-500ms rebuilds in dev and router rebuilt on tracked primitives for simpler code and easier contributions.
AI-written summary · about
chapters (17)
- 0:00Introduction and AMA setup
- 0:20Future of Ember router
- 3:28Embroider V support status
- 5:54Ember animation and Liquid Fire
- 8:24Simplifying the Ember router
- 11:10Why people avoid Embroider
- 13:43Custom Embroider macros
- 16:12Staying motivated in open source
- 19:02Polaris Edition scope and coherence
- 21:32Making Ember mainstream
- 24:26Fear of Ember dying
- 27:35Embroider rebuild speed benefits
- 30:25Making contributions easier
- 33:35Ember steering vs core teams
- 36:24Personal productivity workflow
- 39:12High-impact Ember work
- 41:37Closing remarks and thanks
