Javascript and the Polyglot Web
summary
History traces JavaScript from a two‑week origin to yearly ECMAScript releases, explains why asm.js leads to WebAssembly, and shows concrete wins: Native Client/PNaCl ambitions, a real 5‑6x speedup from Rust+Wasm on a source‑map hot path, and an opposing pure‑JS rework that matches performance with heavy VM‑aware tricks. Practical barriers remain — the anyref proposal and object/string interop — and concrete serverless, edge, and blockchain runtimes already run Wasm in production.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:23Javascript and the Polyglot Web
- 1:03The Polyglot Web
- 2:30The Web 1 0
- 4:43Netscape Navigator
- 5:36Microsoft versus Netscape
- 12:26Flash
- 20:40Web Assembly
- 30:29Blockchain
- 31:12Edge Computing
- 31:51Why Would You Want a Polyglot Web
- 34:03Should Webassembly Replace the Javascript
- 39:39Takeaway
related talks
23mWeb Assembly: The Future Of Js And A Multi-Language Web
30mWhy Should You Consider JavaScript on WebAssembly?
03mJavascript in 2016, Beyond Harmony
18mA Brief History of JavaScript
39mFast future with WebAssembly
20mWeb Assembly: The Future of JS and a Multi-Language Web
34mPractical Polyglot WebAssembly
30mThe future of Javascript