Panel
summary
Panel lays out concrete progress and trade offs at TC39: which proposals move (a simplified temporal proposal aimed at browser implementability), which APIs actually change (pattern matching, iterator helpers, string iterability), where libraries step in (ICU4X and a JS polyfill for message format), when WebAssembly is the right polyfill tool, and why some designs are being reversed for compatibility and performance around signals and iteration.
AI-written summary · about
chapters (13)
- 0:00TC39 panel introduction
- 1:07Exciting TC39 proposals
- 5:43TC39 design regrets
- 9:37New web language vs JavaScript
- 12:47ICU for React translations
- 16:00Commercial interests in standards
- 18:54JavaScript called ECMAScript
- 19:36Polyfills and WebAssembly
- 21:45Task groups shaping TC39
- 23:37Proposal standardization timeframes
- 26:50Browsers rejecting features
- 28:57Signals vs Virtual DOM
- 30:21Closing remarks
