Approaching the Javascript Singularity

on YouTube ↗33m

" summary

Claim: WebAssembly yields near‑native speed and is already replacing some native modules while remaining sandboxed so it cannot access serial ports or other system APIs. Evidence: Rust-compiled WebAssembly sourcemap parser 8× faster in Firefox, N-API landed in Node 10 enabling a stable ABI for native addons, and WebAssembly modules appear in npm with webpack experimentation. Notes: worker threads / web workers converge runtimes, Deno adopts fetch, and Electron’s lessons push platform integration rather than perpetual bridges.

AI-written summary · about

" chapters (12)

1. 0:00Introduction
2. 1:35JavaScript singularity matters
3. 3:02JavaScript performance history
4. 7:38WebAssembly performance
5. 11:10WebAssembly use cases
6. 14:00WebAssembly Node.js access
7. 17:17ES modules code separation
8. 20:48WebAssembly NPM integration
9. 23:29Worker threads concurrency
10. 26:23Browser Node.js experiments
11. 29:19JavaScript Node.js future
12. 30:41JavaScript singularity closing

" related talks

• 37mApproaching the JavaScript SingularityIstván Szmozsánszky "Flaki" · JSHeroes 2019
• 16mWhy WebAssemblyMiguel Useche · JSConf Mexico 2020 Virtual Edition
• 30mWhy Should You Consider JavaScript on WebAssembly?Saúl Cabrera, Angel M De Miguel Meana · Open Source Summit Europe 2023
• 40mJavascript and the Polyglot WebMassimiliano Mantione · JSDay 2019
• 32mWebAssembly vs JavaScript: Which Is Faster?Alexandr Skachkov · OdessaJS 2018
• 36mHelp me WebAssembly, You're My Only HopeJay Phelps · DinosaurJS 2018
• 23mHow Webassembly Will Change the Way You Write JavascriptSeth Samuel · EmpireNode 2016
• 33m"Is WebAssembly the killer of JavaScript"Boyan Mihaylov · Codemotion Milan 2015