Uploaded October 2026 | Updated November 2026, 3 days ago
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.
Chapters:
00:00 Welcome to WebAssembly Unleashed
00:34 Meet Ryan Hunt (Mozilla): SpiderMonkey + Firefox Wasm lead
01:13 Why Ryan’s still bullish on Wasm (and why it’s “designed”)
03:03 Reality check: Wasm adoption is steady, not a hype takeover
05:02 Why more Devs don’t use Wasm: Missing features + long timelines
06:31 Biggest friction: Toolchains, headers, and a fragmented ecosystem
07:57 The performance wall: Crossing Wasm ↔ JS for Web APIs
08:55 Component Model: The “exe on the web” idea
12:19 Why compilers want a real target/ABI (not “generate JS”)
14:02 Firefox prototype results: Components beat JS by ~10–20%
17:50 Standards drama: “Why not just make JavaScript faster?”
21:31 What’s next: Mozilla’s Web Developer Preview plan
23:32 SharedArrayBuffer “for the people”? Reality + blockers
For more from F5's Office of the CTO visit the following sites:
Blogs - f5.com/company/octo
Reports - f5.com/services/resources/reports
Meet Your Hosts:
Joel Moses | linkedin.com/in/joelmoses | community.f5.com/users/joel_moses/398372
Oscar Spencer | twitter.com/oscar_spen | linkedin.com/in/oscarspen
⬇️⬇️⬇️ JOIN THE COMMUNITY! ⬇️⬇️⬇️
DevCentral is an online community of technical peers dedicated to learning, exchanging ideas, and solving problems - together.
Find all our platform links ⬇️ and follow our Community Evangelists! 👋
➡️ DEVCENTRAL: community.f5.com
➡️ YOUTUBE: youtube.com/devcentral
➡️ LINKEDIN: linkedin.com/showcase/f5-devcentral
➡️ TWITTER: twitter.com/devcentral
Your Community Evangelists:
👋 Jason Rahm: linkedin.com/in/jrahm | twitter.com/jasonrahm
👋 Buu Lam: linkedin.com/in/buulam | twitter.com/buulam
👋 Chase Abbott: linkedin.com/in/chaseabbott1
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.
Chapters:
00:00 Welcome to WebAssembly Unleashed
00:34 Meet Ryan Hunt (Mozilla): SpiderMonkey + Firefox Wasm lead
01:13 Why Ryan’s still bullish on Wasm (and why it’s “designed”)
03:03 Reality check: Wasm adoption is steady, not a hype takeover
05:02 Why more Devs don’t use Wasm: Missing features + long timelines
06:31 Biggest friction: Toolchains, headers, and a fragmented ecosystem
07:57 The performance wall: Crossing Wasm ↔ JS for Web APIs
08:55 Component Model: The “exe on the web” idea
12:19 Why compilers want a real target/ABI (not “generate JS”)
14:02 Firefox prototype results: Components beat JS by ~10–20%
17:50 Standards drama: “Why not just make JavaScript faster?”
21:31 What’s next: Mozilla’s Web Developer Preview plan
23:32 SharedArrayBuffer “for the people”? Reality + blockers
For more from F5's Office of the CTO visit the following sites:
Blogs - f5.com/company/octo
Reports - f5.com/services/resources/reports
Meet Your Hosts:
Joel Moses | linkedin.com/in/joelmoses | community.f5.com/users/joel_moses/398372
Oscar Spencer | twitter.com/oscar_spen | linkedin.com/in/oscarspen
⬇️⬇️⬇️ JOIN THE COMMUNITY! ⬇️⬇️⬇️
DevCentral is an online community of technical peers dedicated to learning, exchanging ideas, and solving problems - together.
Find all our platform links ⬇️ and follow our Community Evangelists! 👋
➡️ DEVCENTRAL: community.f5.com
➡️ YOUTUBE: youtube.com/devcentral
➡️ LINKEDIN: linkedin.com/showcase/f5-devcentral
➡️ TWITTER: twitter.com/devcentral
Your Community Evangelists:
👋 Jason Rahm: linkedin.com/in/jrahm | twitter.com/jasonrahm
👋 Buu Lam: linkedin.com/in/buulam | twitter.com/buulam
👋 Chase Abbott: linkedin.com/in/chaseabbott1





![Optimizing AI Inference using NGINX Gateway Fabric
Running AI inference workloads on Kubernetes presents unique challenges. Traditional load balancing methods designed for standard web APIs simply fall short when it comes to the nuanced resource management required for generative LLMs.
In this demo, we explore how the NGINX Gateway Fabric Inference Extension transforms your Kubernetes environment by acting as a dedicated Inference Gateway. Discover how to move beyond basic proxying by utilizing a powerful two-stage architecture—combining standard HTTPRoutes with the InferencePool CRD and Endpoint Picker. This allows NGINX to make intelligent, real-time routing decisions based on queue depth and GPU availability.
What you will see in this demo:
0:11 - The Challenges of AI Workloads: Why standard load balancing fails for GPUs.
0.51 - Two-Stage Orchestration: Understanding the InferencePool and Endpoint Picker.
2:24 - Model-Aware Routing: Inspecting traffic paths to offload lightweight tasks to CPUs and reserve premium GPUs for heavy text generation.
3:46 - Canary Testing: Validating new models safely using native 90/10 traffic splitting.
4:49 - Cost Optimization: Using custom HTTP headers to guarantee SLAs and reserve compute for mission-critical queries.
🔗 Helpful Links & Resources:
NGINX Gateway Fabric Documentation: [https://docs.nginx.com/nginx-gateway-fabric]
GitHub Repository / Lab Guides: [https://github.com/nginx/nginx-gateway-fabric]
Notes:
- Contributed by: Akash Ananthanarayanan
- Related Article: None
⬇️⬇️ JOIN THE COMMUNITY! ⬇️⬇️⬇️
DevCentral is an online community of technical peers dedicated to learning, exchanging ideas, and solving problems—together.
Find all our platform links ⬇️ and follow our Community Evangelists! 👋
➡️ DEVCENTRAL: https://community.f5.com
➡️ YOUTUBE: https://youtube.com/devcentral
➡️ LINKEDIN: https://www.linkedin.com/showcase/f5-devcentral/
➡️ X: https://x.com/devcentral
Your Community Evangelists:
👋 Jason Rahm: https://www.linkedin.com/in/jrahm/ | https://x.com/jasonrahm
👋 Buu Lam: https://www.linkedin.com/in/buulam/ | https://x.com/buulam
👋 Chase Abbott: https://www.linkedin.com/in/chaseabbott1 Optimizing AI Inference using NGINX Gateway Fabric](https://i.ytimg.com/vi/TReqi7V8yoI/mqdefault.jpg)




