Keynote Part 1
summary
Polaris brings a concrete migration: Ember 5.0 aligns with modern tooling by landing Ember template imports so templates live in JS files via a template tag, letting helpers, modifiers and small components share scope. A unified resources API replaces class helpers, services and modifiers with teardown and lifecycle, enabling route-level code splitting so code and data fetch in parallel. Starbeam offers a universal reactive core, import maps enable hash app imports, and TypeScript inference works without noisy type annotations.
AI-written summary · about
chapters (22)
- 0:00Ember community sustainability
- 1:42Ember in family life
- 3:07Ember architectural blocks
- 4:33Rails inspiration for Ember
- 5:56Keynote overview Polaris intro
- 6:58Shared tooling migration
- 7:19Template tag components
- 10:53Modifiers lifecycle
- 13:39Template tag vs JSX
- 16:47Template imports tooling
- 17:07Resources unifying Ember
- 23:08Starbeam reactivity
- 24:34Routing code splitting
- 31:11URL stability routing
- 33:18Ember ecosystem sustainability
- 35:24Ember’s relevance uniqueness
- 36:48No ejection policy format
- 39:16CSS tooling integration
- 41:04Ember building blocks services
- 42:28Backward compatibility migration
- 44:12Polaris solution incoherence
- 46:38Conclusion transition
