The What's, Why's, and How's of Running WebAssembly in Go
summary
Shows a small Go library called reactor Go library that embeds WebAssembly modules (wasm) using selectable runtimes like wasmtime/wasmedge, exposes explicit host capabilities (HTTP, file, sockets) and enforces a deny‑by‑default sandbox. Demonstrates factorial workloads compiled from Rust, TinyGo and AssemblyScript: running factorial(5000) 100,000 times yields roughly 1700 ms vs 4600 ms between Rust/TinyGo and AssemblyScript. Covers hot‑swap of modules, WASI/capability caveats, multi‑tenant limits and the subocli build flow.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:48What is WebAssembly?
- 2:58Why Wasm makes sense elsewhere
- 6:16Wasm vs Docker
- 24:38Use-cases
- 26:38Caveats
related talks
29mExperimenting with Golang and Webassembly
25mWebAssembly with Go: Powering the Web with Speed and Efficiency
37mGo, WebAssembly!
29mWhat is Web Assembly and Why Should you Care?
48mWebAssembly Beyond the Browser
50mWeb Assembly
40mWebAssembly - The Future of Distributed Computing
08mRunning Go in Browsers Using WASM
