Level-Up Embedded Development with WebAssembly
summary
Claims that embedding WebAssembly on constrained devices moves decision making to the edge, cutting upstream bandwidth and enabling local model updates; cites a $3.8M raise and Peter Levine’s “data will be stuck at the edge” prediction. Demonstrations use runtimes like wasm‑micro‑runtime, wasm3, Wasmtime and Wazero, with a micro:bit running a tiny‑Go app that exposes buttons, LED and Bluetooth via a device interface and achieves state synchronization in ~15–20 lines. Notes interpreter vs JIT tradeoffs and 4KB vs 64KB page constraints.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:36What Is My Cloud Made of
- 6:02The Difference between Hard Real-Time and Soft Real-Time
- 16:10Webassembly
- 26:19Using the Webassembly Micro Runtime
- 27:09Compilation Style
- 28:31Webassembly Interface Types
- 32:53Webassembly Micro Runtime
- 40:15Debugging
related talks
26mWebAssembly for a Reactive Internet of Things
34mEmbedding WASM in the Future
37mBuilding a better web with WebAssembly at the edge
25mFrom Cloud to Edge computing - Unleashing the power of WebAssembly at the edge
37mDecoding the hype behind WebAssembly: Looking under the hood
36mWasmer Things: An Upside-Down Guide to WebAssembly
41mDemystifying WebAssembly, Through the Eyes of A Beginner
12mSponsored Keynote: WebAssembly: The future of distributed computing