Keynote: The Path to Components
summary
Proposal splits WASI into a foundational component model implemented by engines and a higher-level WASI layer; it replaces POSIX-style linking with parametric linking so units can instantiate and wire other units, avoids gluing via files by introducing value and resource types (handles, futures, streams), and provides WIT + wit-bindgen/wit-component toolchain to generate Rust/JS bindings and bundle components. Wasmtime already implements large parts; milestone for Q1 targets sync components (parametric linking, value/resource/handle types) with async futures/streams following.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:28MVP
- 1:01Portable Interface
- 1:34System Interface
- 3:15Posix
- 3:44Why are people putting WASM into production
- 4:43Linking via the file system
- 5:10Parametric Linking
- 6:41Complex Data
- 7:57Value Types
- 9:03File Describing
- 9:49Resource and Handle Types
- 11:09Low Level Concurrency
- 12:19Future Streams
- 14:38Components OMG
- 15:13The Developer Experience
- 17:09Worlds
- 21:18Virtualization
- 23:41The Big Picture
- 24:35Status
related talks
30mKeynote: What is a Component (and Why)?
56mKEYNOTE: WebAssembly Update: The Proposals, Wasi, And The Component Model
13mKeynote: Are We Componentized Yet?
08mKeynote: WASI Standards and the Component Model: Transforming Application Development Forever
52mWhat is a WebAssembly component (and why?)
21mKeynote: WASI - A new kind of system interface & what it means for cloud native
30mComponents, WebAssembly’s Docker’s Moment
25mKeynote: View from Above: A Birds-eye View of the Wasm Landscape and Where It's Heading