Beyond the browser: Moving forward with a more Declarative Future with WebAssembly
summary
WebAssembly moves beyond the browser into edge and serverless with concrete numbers and tools: Rust compiled via wasm32-wasi using cargo produces tiny modules that run at near native speed, FFmpeg ported as FFmpeg.wasm performs in-browser video editing, and cold starts drop compared with containers that take 10–20 seconds. Runtimes like wage plus WASI provide system calls, Spin and containerd/Kubernetes integrations let wasm run in cloud workloads, and the component model enables polyglot interoperability between modules.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:06What is WebAssembly
- 3:11WebAssembly misconceptions
- 4:14Origins of WebAssembly
- 6:45Why WebAssembly outperforms JS
- 8:28WebAssembly vs Java Virtual Machine
- 9:34WebAssembly in practice
- 12:47WebAssembly beyond browser
- 13:51Evolution to WebAssembly
- 15:57Rust to WebAssembly
- 17:02WASI and WebAssembly System Interface
- 18:24WebAssembly vs Docker
- 19:49Deploying in Kubernetes
- 20:51WebAssembly Component Model
- 23:23Polyglot with Components
- 24:25Future of WebAssembly & Q&A
related talks
48mWebAssembly Beyond the Browser
33mWebAssembly: The Next Frontier of Cloud Computing
38mWebAssembly beyond the browser
42mWebAssembly beyond the browser
53mWebAssembly – To the browser and beyond!
37mBuilding a better web with WebAssembly at the edge
36mWebAssembly Everywhere, All at Once
19mWebAssembly's Journey Beyond the Browser