WebAssembly beyond the browser
summary
Claim: WebAssembly modules compile once and run everywhere but current limits matter. Examples include compiling Rust to wasm32-wasi, running the same .wasm with wasmtime/wasmer while mapping host directories to write files, and packaging that .wasm into Docker (Docker 4.21+, containerd + runwasi) to run on Kubernetes. Missing pieces: WASI currently lacks standard sockets and threads, so HTTP is often handled by WAGI’s stdout/CGI model or frameworks like Spin. Results: faster startup, smaller binaries, deny‑by‑default sandboxing.
AI-written summary · about
chapters (11)
- 0:00WebAssembly beyond browser
- 3:23WebAssembly on server
- 7:16From hardware to WebAssembly
- 8:20WebAssembly use cases
- 11:07WebAssembly runtimes
- 16:06Rust to WebAssembly demo
- 19:58WebAssembly in Docker/K8s
- 26:19HTTP with WAGI
- 29:30Wazix POSIX extensions
- 30:11Frameworks & language support
- 34:26Conclusion








