TC39 Demystified
summary
Explains how JavaScript changes are actual GitHub pull requests (see tc39/ecma262 repo), run through quarterly meetings plus monthly subteam and incubator calls, and decided by consensus without votes; editors, champions and reviewers shepherd proposals through stage 0–3; examples: Temporal stage 3 is already implemented in engines, records & tuples stage 2 is available via Babel, and decimal stage 1 is still design work; communication happens on Discourse and MDN and via focused task groups.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:52About TC39
- 4:44Who is TC39?
- 7:01Where do things happen?
- 8:05What do TC39 members do?
- 11:53When does all this happen?
- 14:58How do things happen?
- 17:33Stage process
- 20:46Building consensus
- 23:08A deeper look into stage process
- 27:01Conclusion
related talks
20mBrief intro to TC39 and how it works
37mTC39 - From the Proposal to ECMAScript - Step by Step
21mTC39: How we work, what we are working on & how you can get involved
43mWhat's up TC39
30mTC39 Panel
31mStandardizing JavaScript - a Look at Ecma and TC39
14mStandardaizing JavaScript: Call for PL researchers
40mSubjective Takes on the TC39 Spec