ES X
summary
Covers the current status of ECMAScript proposals and when they land in engines: async iterators (for await...of) are finished (stage 4) and implemented in browsers, letting readable streams be iterable; private fields (using #) and decorators are around stage 3 with concrete syntax; optional chaining and numeric separators are progressing through the pipeline. Explains TC39 staging rules, an approximate one-year rollout cadence per feature, concrete code-level effects, and warns that Babel can polyfill many proposals but stage‑1 features may change semantics and are risky to rely on.
AI-written summary · about
chapters (10)
- 0:00Welcome
- 1:16ECMAScript vs JavaScript
- 3:06TC39 role
- 7:42Babel despite ES6+
- 8:49Async iterators in ES2018
- 15:44Private class fields
- 21:22Decorators for code
- 25:14Optional chaining
- 27:44Numeric separators
- 28:48Conclusion & Q&A
related talks
11mWhat's cooking for JavaScript: a look at current TC39 proposals
43mWhat's up TC39
21mTC39: How we work, what we are working on & how you can get involved
40mProposals in This Day & Age, Taking Steps to the Next Stage
50mProposals in this day & age, taking steps to the next stage
47mECMAScript: latest and upcoming features
37mThe future of ES6
06mWhat’s new in ECMAScript?
