TC39 Panel
summary
Standards work follows a staged pipeline: ideas start at stage zero and only reach the standard after stage three implementations and conformance tests. Proposals commonly take years (optional chaining spans ~3+ years), committees meet six times a year and typically advance one stage per meeting so fastest progress is ~8 months. Conformance relies on test262 and test262.report, engines and tools (V8, SpiderMonkey, Babel, XS) must agree, and landing requires two implementations and real-world browser/tool integration.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:12Rob Palmer
- 3:35How Does a Feature Move through the Committee through the Proposal Process
- 8:42How Do Proposals Work on Internationalization
- 12:03Conformance Tests
- 22:04Syntax Complexity
- 24:33Engaging with Users on Github
- 26:18What Are the Goals for the Committee
- 36:45Internationalization
- 40:18What Is the Difference between Tc39 and Groups like W3c
- 45:54Do any of You Have a Favorite Javascript Joke
related talks
37mTC39 - From the Proposal to ECMAScript - Step by Step
21mTC39: How we work, what we are working on & how you can get involved
20mBrief intro to TC39 and how it works
30mTC39 Panel
28mTC39 Demystified
43mWhat's up TC39
14mStandardaizing JavaScript: Call for PL researchers
50mProposals in this day & age, taking steps to the next stage