The news of the death of JavaScript has been greatly exaggerated

on YouTube ↗19m

" summary

Gives a 1995–2025 timeline showing concrete attempts to replace JavaScript: browser forks like JScript/VBScript, plugin ecosystems (Flash and Java applets that repeatedly fail due to security and user install burden), and compilation targets such as GWT and Blazor that produce multi‑MB generated bundles and poor DOM access. Notes milestones (1999 JSON and Node.js, ES6 and annual releases) and two real wins from the ecosystem: TypeScript mainstream and WebAssembly for heavy compute but it needs JS for DOM. Concludes JavaScript remains the web’s runtime.

AI-written summary · about

" chapters (11)

1. 0:00Introduction and welcome
2. 1:06Programming trends 2025-2035
3. 2:56JavaScript's first 30 years
4. 6:08JavaScript's developer struggles
5. 7:11Browser-based killers
6. 9:00Plugin-based approaches
7. 11:10Compilation targets
8. 14:02WebAssembly's role
9. 15:06New web standards
10. 16:14Why JavaScript won't die
11. 17:38Q&A

" related talks

• 49mNot Your Father's Java, Not Your Mother's JavaScriptDmitry Chuyko · JCON Europe 2023
• 38mJavascript Considered...UsefulJenn Schiffer · JSConf EU 2019
• 40mJavascript and the Polyglot WebMassimiliano Mantione · JSDay 2019
• 23mThe third age of JavaScript: Three years inswyx · Reactathon 2022
• 42mKeep Betting on JavaScriptKyle Simpson · JSNation 2019
• 18mA Brief History of JavaScriptBrendan Eich · dotJS 2017
• 26mThe Evolution of JavaScriptJemima Abu · JSWorld Conference 2022
• 27mJavascript at 20Brendan Eich · JSConf Colombia 2015