What is a WebAssembly component (and why?)
summary
Defines a new module format that layers typed interfaces (WIT) and multi-module composition on top of core WebAssembly so each submodule keeps its own linear memory, values copy or pass as handles, and resources are explicit; claim: this lets you get SDKs for free, secure polyglot packages, modularity without microservices and cheap virtual platform layering. Implementations and tools include Wasmtime/WasmEdge, a JCO transpile polyfill (runs in Node/browser), wasi SDK/virt wrappers, componentize-js/py, wm compose, warg + OCI component artifacts; Preview 2 is shipping and Preview 3 adds native futures/streams.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:06WebAssembly capabilities
- 15:07Current limitations
- 22:06WebAssembly components
- 33:33Lightweight sandboxing
- 37:46Preview 2 and future
- 42:45Q&A
related talks
18mAn introduction to the WebAssembly component model
30mKeynote: What is a Component (and Why)?
30mComponents, WebAssembly’s Docker’s Moment
16mThe nuts and bolts of WebAssembly's component model
34mWasm Components for Every Language
01h 01mAn introduction to WebAssembly components
56mKEYNOTE: WebAssembly Update: The Proposals, Wasi, And The Component Model
39mJavaScript Toolchain for WebAssembly Components