Uploaded September 2026 | Updated November 2026, 3 hours ago
WebAssembly keeps expanding beyond its original “run C/Rust in the browser” story, and this episode is a tour through the ideas and tooling that are shaping what comes next. Joel Moses and Oscar Spencer are joined by Conrad Watt, PhD., co-chair of the W3C WebAssembly Community Group, a key contributor to the formal memory and concurrency models, and an assistant professor at NTU Singapore, to talk about how formal methods, mechanized proofs, and specification engineering are influencing the evolution of Wasm.
Conrad recounts how his academic work intersected with WebAssembly’s earliest formal semantics and why Wasm remains such a fertile “lens” for programming language research, spanning type systems, concurrency, and security. A central thread is the concurrency story: how WebAssembly threads grew from the JavaScript shared-memory model, what makes memory growth semantics difficult, and why getting threads fully integrated into the published W3C specification still has real engineering and tooling hurdles.
The episode then zooms in on SpecTec, the domain-specific language now used to render the official WebAssembly 3.0 specification. Conrad explains why it exists, what problems it solves compared to raw LaTeX, and what remains unfinished, including the long-term goal of generating executable and provable semantics directly from the spec. They also talk about the looming challenge every web standard faces: specs only add features, they rarely remove them, and the community still doesn’t have a clean answer for avoiding complexity collapse.
Finally, the episode closes by looking at Wasm’s intersection with AI, where its portability and safety model are strong assets, but GPU integration remains a key bottleneck, and by discussing how AI is changing education, including why in-person exams are making an unexpected comeback. If you’re interested in the research backbone of WebAssembly, this episode is the roadmap.
Chapters:
00:00 Welcome to WebAssembly Unleashed
00:23 What is WebAssembly now (and why the name is misleading)
01:38 Finding bugs in early Wasm formal math
04:16 Why Wasm stays academically interesting: Types, security, threads
05:52 The concurrency journey: Shared memory, threads, and what’s missing
08:16 SpecTec explained: Why Wasm moved beyond painful LaTeX specs
10:56 Can SpecTec replace the OCaml reference interpreter? (Not yet)
13:15 Keeping the spec from collapsing as features explode
14:54 Exciting research projects happening across academia
16:44 Wasm beyond the browser: Cloud, embedded, sandboxing (RLBox)
18:21 The importance of the WebAssembly Community
20:16 Research Day + teaching with Wasm: New learning tools & IDEs
22:31 Wasm + AI: Why it’s promising, and the GPU access bottleneck
25:55 “Sneak in one feature”: Thread spawning, and why it’s hard
Check out the recordings from Wasm Research Day 2026: youtube.com/playlist?list=PLUO8XobXx1SE
For more from F5's Office of the CTO visit the following sites:
Blogs - f5.com/company/octo
Reports - f5.com/services/resources/reports
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 keeps expanding beyond its original “run C/Rust in the browser” story, and this episode is a tour through the ideas and tooling that are shaping what comes next. Joel Moses and Oscar Spencer are joined by Conrad Watt, PhD., co-chair of the W3C WebAssembly Community Group, a key contributor to the formal memory and concurrency models, and an assistant professor at NTU Singapore, to talk about how formal methods, mechanized proofs, and specification engineering are influencing the evolution of Wasm.
Conrad recounts how his academic work intersected with WebAssembly’s earliest formal semantics and why Wasm remains such a fertile “lens” for programming language research, spanning type systems, concurrency, and security. A central thread is the concurrency story: how WebAssembly threads grew from the JavaScript shared-memory model, what makes memory growth semantics difficult, and why getting threads fully integrated into the published W3C specification still has real engineering and tooling hurdles.
The episode then zooms in on SpecTec, the domain-specific language now used to render the official WebAssembly 3.0 specification. Conrad explains why it exists, what problems it solves compared to raw LaTeX, and what remains unfinished, including the long-term goal of generating executable and provable semantics directly from the spec. They also talk about the looming challenge every web standard faces: specs only add features, they rarely remove them, and the community still doesn’t have a clean answer for avoiding complexity collapse.
Finally, the episode closes by looking at Wasm’s intersection with AI, where its portability and safety model are strong assets, but GPU integration remains a key bottleneck, and by discussing how AI is changing education, including why in-person exams are making an unexpected comeback. If you’re interested in the research backbone of WebAssembly, this episode is the roadmap.
Chapters:
00:00 Welcome to WebAssembly Unleashed
00:23 What is WebAssembly now (and why the name is misleading)
01:38 Finding bugs in early Wasm formal math
04:16 Why Wasm stays academically interesting: Types, security, threads
05:52 The concurrency journey: Shared memory, threads, and what’s missing
08:16 SpecTec explained: Why Wasm moved beyond painful LaTeX specs
10:56 Can SpecTec replace the OCaml reference interpreter? (Not yet)
13:15 Keeping the spec from collapsing as features explode
14:54 Exciting research projects happening across academia
16:44 Wasm beyond the browser: Cloud, embedded, sandboxing (RLBox)
18:21 The importance of the WebAssembly Community
20:16 Research Day + teaching with Wasm: New learning tools & IDEs
22:31 Wasm + AI: Why it’s promising, and the GPU access bottleneck
25:55 “Sneak in one feature”: Thread spawning, and why it’s hard
Check out the recordings from Wasm Research Day 2026: youtube.com/playlist?list=PLUO8XobXx1SE
For more from F5's Office of the CTO visit the following sites:
Blogs - f5.com/company/octo
Reports - f5.com/services/resources/reports
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










