New Adventures for WASM
summary
Concrete progress and concrete gaps appear: Firefox already ships streaming compilation and a baseline compiler and claims JS↔Wasm calls as fast or faster than JS→JS, Chrome and others add caching of compiled code, and Rust rewrites show 11× and 86× speedups for real projects; proposals for threads and SIMD are near or under active development, SharedArrayBuffer returns, a 64-bit addressing proposal (wasm64) is planned, a GC prototype exists, exception handling and better debugging remain work in progress, and a cross‑runtime WASI for portable, sandboxed system APIs is advancing.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:24What Is Web Assembly
- 1:36Webassembly Story
- 2:25Skills Needed
- 3:49Linear Memory Model
- 5:4264-Bit Addressing
- 6:14Streaming Compilation
- 7:06Skip Compiling
- 8:01Firefox Added Streaming Compilation
- 12:16Rewriting Parts of J / S Frameworks
- 13:31Garbage Collection
- 15:55The Security Model
- 16:13Portability
- 17:37Security
- 24:43Security Model
related talks
33mWebAssembly's Post-MVP Future
45mWebAssembly's Post-MVP Futurer
34mPanel Discussion: Browsers & Wasm
37mBeyond the browser: Moving forward with a more Declarative Future with WebAssembly
39mFast future with WebAssembly
21mHit the Ground Running with WebAssembly
36mHelp me WebAssembly, You're My Only Hope
17mA case for Web Assembly