Lightning Talk: WebAssembly from the Inside Out
summary
Explains how the wazero runtime implements WebAssembly calls end-to-end: modules decode and validate at load time, compile to an internal IR that an interpreter runs or an amd64 backend emits as native code, and a trampoline switches between compiled Wasm and Go host functions by passing identifiers and marshaling parameters. Claims no cgo dependency because it is pure Go, supports context cancellation, can run wasm inside wasm, and notes a multi-pass optimizing compiler is in progress.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:43What is Wero
- 2:07WebAssembly compilation
- 3:08Runtime invocation
- 4:59Pure Go runtime
- 6:25Wero’s portability
- 7:30Q&A
related talks
38mWebAssembly for the backend
37mDecoding the hype behind WebAssembly: Looking under the hood
16mWhy WebAssembly
08mLightning Talk: Build trusted cloud apps with Wasm: WebAssembly Micro Runtime is ready
29mWhat is Web Assembly and Why Should you Care?
40mWebAssembly - The Future of Distributed Computing
49mWasmer Things: An Upside-Down Guide to WebAssembly
44mWebAssembly: the browser is now a real virtual machine
