Final Thoughts
summary
A panel answers concrete tradeoffs: JavaScript evolution accepts messy legacy and deprecation rather than wholesale removal, illustrated by navigator.enableTaint which removal once broke “half the web”; Rust targets systems safety but may compile to JS so expect a Rust to JavaScript compiler sometime; type efforts split between Typescript and flow with engines reserving the colon syntax; standards move toward a rapid release footing (ES7) instead of giant, slow projects.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:32Brandons Tweet
- 1:42Good and Bad Parts
- 3:40Removing Things Being Difficult
- 5:38Rust vs JavaScript
- 6:33Types in JavaScript
- 8:04Biggest lessons from TC39
related talks
40mKeep Betting On JavaScript
23mThe third age of JavaScript: Three years in
53mPanel Discussion
35mJSParty Live on the Future of JavaScript
26mJavaScript Won the Web, Rust Is Taking the Critical Path
47mThe Politics of JavaScript
27mWhere is the JavaScript world going?
01h 00mThe State and Future of JavaScript
