Software Engineering Daily WebAssembly 3.0 with Andreas Rossberg
28 snips
Jan 20, 2026 
Andreas Rossberg, a programming languages researcher and architect of WebAssembly, dives into the evolution of this influential technology. He shares insights on the journey from WebAssembly's early designs to its powerful 3.0 spec, which introduces garbage collection and richer reference types. Rossberg explains how WebAssembly excels in compute-heavy applications compared to JavaScript. He also discusses its future capabilities, such as threads and effect handlers, and touches on non-web applications like edge computing and blockchain.
AI Snips
Chapters
Transcript
Episode notes
Community And Vendors Drive The Roadmap
- Feature priorities came from compiler writers, engine authors, framework teams, and sometimes CPU vendors pushing hardware features.
- GC, exceptions, SIMD, and threads all progressed from community needs and implementation experience.
Prefer JS For DOM-Heavy Apps
- Use JavaScript for heavy DOM-centric apps because DOM APIs are designed for JS and glue code from Wasm adds friction.
- Target WebAssembly when portability, sandboxing, or heavy compute matter more than tight DOM integration.
No Ambient Capabilities: Imports Only
- WebAssembly has no ambient capabilities; all host interactions must come through explicit imports.
- Component model and agreed interfaces may give Wasm nicer, language-agnostic access to web APIs in future.
