The State and Future of JavaScript
summary
Standards process chronicle: ES4 gets abandoned, a minimalist ES3.1 becomes the candidate for a fifth edition and strict mode is the opt‑in repair path; security hardening shows up in work like Caja and AdSafe and Facebook sandboxing; the top bug is 0.1 + 0.2 ≠ 0.3, IBM pushes IEEE 754R dec128, the committee proposes faster alternatives (Dec64, 9E6), and block scope (let/const) plus better argument handling land as practical fixes.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 2:03The Fellowship of the Ring
- 3:35ECMO Technical Committee 39
- 10:12ES31 Alternative
- 12:16Joint Meetings
- 14:29Project Slipping
- 16:25Decimal Arithmetic
- 19:04Binary FloatingPoint
- 19:46IBMs Proposal
- 25:16Decimal Library
- 26:35Decimal
- 31:32Appeal to IBM
- 32:13Two languages
- 33:59Harmony
- 35:03Suck Less
- 40:05Block Scoped
- 41:01Syntax
- 41:43Correspondence
- 43:32Language Design
- 44:15Ajax
- 45:08Conclusion
- 45:45Will it succeed
- 46:32Tradeoffs
- 47:33People
- 48:11The hard thing
- 49:07Betrayal
- 51:40Patent System
- 52:48ECMO
- 53:46Questions
- 54:32Why did we remove arguments
- 57:27When will it hit the streets
related talks
40mJavaScript: The Standard's Evolution When Nobody Cares
23mThe third age of JavaScript: Three years in
58mKeep Betting On JavaScript
23mES13 and Beyond: The Future of JavaScript
32mWhat's Coming Next to JavaScript?
32mJS Responsibilities
18mA Brief History of JavaScript
25mFuture JavaScript: what is still missing?