Aligning Ember with Web Standards
summary
Claim: Ember must incrementally reconfigure around emerging JavaScript standards rather than wait for a big-bang ES release. Evidence: Babel transpiles ES2015 to ES5 but varying browser support means selective transpilation is needed. Hard limits: proxies can't be polyfilled and new syntax requires parsing. Examples: prototype migration for components using Glimmer reduces observers so ES classes become practical. Data: community survey yields 900+ responses with about 75% on the latest Ember.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:45JavaScript Standardization
- 3:03Living Document
- 7:49Participants Win
- 8:19Polyfill
- 9:06ES2015
- 14:37Classes
- 18:24Aligning
- 21:55Community Survey
