The Future Of Templating In Ember
summary
Overview of concrete language and runtime changes: Ember moves templates toward explicit interfaces with @-arguments (RFC 276 landed in 3.4) and a required resolution plan (RFC 308), adds angle-bracket invocation and splattributes plus outer-HTML semantics (3.4), and proposes element-level DOM hooks via element modifiers (RFC 353) and an element modifier manager (RFC 373). Glimmer VM enables bytecode, rehydration, incremental rendering and WebAssembly experiments. RFCs for named blocks (317) and module-imports for addons (367) aim to make templates statically resolvable.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker background
- 1:52Why Ember has templating
- 3:18Design principles behind templating
- 7:13Simplicity vs ease in templating
- 10:01Evolution of Ember’s rendering engine
- 13:37Clarity in future templating
- 14:41RFC 276: Arguments proposal
- 16:28RFC 308: Required syntax
- 18:56Components and angle bracket invocation
- 21:21Splat attributes in components
- 22:45RFC 311: Custom components
- 24:31Long-term RFCs and future ideas
- 27:22Element modifiers and RFC 373
- 29:10RFC 226: Named blocks
- 32:02RFC 367: Module unification
- 34:07Recap of future templating changes
