TC39 - From the Proposal to ECMAScript - Step by Step
summary
Explains TC39’s concrete pipeline: stage 0–4 proposals move through consensus at 4–8 plenaries per year, with tiny edits finishing in ≈1 year while big features take multiple years. Shows real proposals and outcomes: Type Annotations treat annotations as runtime-ignored text to remove compile steps; Temporal and Intl.DurationFormat land as comprehensive date/time APIs; a module proposal defers evaluation to avoid startup cost. Cites tools and artifacts: Test262 harness, Babel, ESMatan, and meetings on Zoom/Jitsi.
AI-written summary · about
chapters (13)
- 0:00Intro
- 3:10Terminology
- 4:20How TC39 works
- 7:01Stages
- 9:26Type annotations
- 11:18Pattern matching
- 15:13Fairing model evaluation
- 19:38Other proposals
- 23:15ChangeR
- 26:01Getting Involved
- 27:43Advice for Young People
- 29:03TC39 Tools
- 31:59How long does it take
