Wasm Components in Firefox: Faster Web APIs, Better DX | WebAssembly Unleashed

WebAssembly Unleashed is back with a conversation that goes beyond hype and into what’s actually holding Wasm back from broader adoption. Hosts Joel Moses and Oscar Spencer are joined by Ryan Hunt, Senior Software Engineer at Mozilla and lead of the WebAssembly team in Firefox’s SpiderMonkey engine, to discuss the real state of WebAssembly in 2026, what’s working, and what still needs to change.

Ryan shares a grounded view of Wasm’s growth, including surprising usage data showing it’s already present on a meaningful slice of the web, even if most users never notice it. From there, the discussion gets practical: why everyday developers still struggle to adopt Wasm, how toolchain fragmentation slows progress, and why calling web APIs from Wasm can be significantly slower than equivalent JavaScript today.

The centerpiece is the WASI component model and what it could unlock for the browser. Ryan explains how components can function like a true “binary format for the web,” enabling better linking, easier instantiation, and a more standard ABI story that upstream compilers can support directly. He also walks through Mozilla’s Firefox prototype work and performance findings, including the potential for native component support to outperform JavaScript while simplifying development.

The episode closes with what’s next: a Firefox developer preview approach, real-world testing, and community pressure that can move components from theory into practice.