WebAssembly beyond the browser
summary
WebAssembly runs outside the browser with concrete tradeoffs: runtimes like Wasmtime, WasmEdge, Wasmer execute tiny, fast modules that start with almost no cold start and use deny-by-default sandboxing, but system calls are limited because WASI preview1 lacks sockets, threads and GC. Real results: Rust-built wasm containers measure 2.6 MB vs 7 MB (and full examples report 5 MB vs 123 MB) because the runtime lives outside the module. Tooling exists—runD/runi in Docker, Spin, Wagi, Wasix—but language support remains patchy and requires hands‑on testing.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:06Understanding WebAssembly
- 4:38Benefits and core concepts
- 8:44Key use cases
- 11:17Runtimes and development
- 18:59WebAssembly in containers
- 26:23Bridging gaps with tooling
- 30:20Frameworks and languages
- 32:39Conclusion and state of tech
related talks
42mWebAssembly beyond the browser
48mWebAssembly Beyond the Browser
35mWebAssembly beyond the browser
37mBeyond the browser: Moving forward with a more Declarative Future with WebAssembly
33mWebAssembly: The Next Frontier of Cloud Computing
19mWebAssembly's Journey Beyond the Browser
37mBuilding a better web with WebAssembly at the edge
50mWeb Assembly