Towards a Component Model 1.0
summary
Component Model claims readiness for industrial use after Preview 3 adds efficient language-integrated concurrency and a cooperative threads roadmap; a working browser polyfill JCO polyfill already transpiles components to JS and enables importable components. The plan targets 1.0 by adding a lazy ABI option, multi-value returns, error-contexts and a GC ABI, while motivating native browser implementations with telemetry and experiments showing up to ~2x speedups on DOM-heavy workloads. Tooling work includes component “smashing,” guest/host C ABIs, and ecosystem publishing.
AI-written summary · about
chapters (9)
- 0:00Need for Component Model 1.0
- 6:11Timeline and goals
- 9:19Improving Component Model ABI
- 14:13Native browser support
- 18:05Easier implementation
- 23:20Growing ecosystem
- 25:05Expressivity gaps
- 29:59Call to action
- 30:40Q&A
related talks
30mComponent Model in Software Defined Vehicles
35mComposable Concurrency for WebAssembly Components
32mThreading the needle with concurrency and parallelism in the Component Model
13mKeynote: Are We Componentized Yet?
30mKeynote: What is a Component (and Why)?
52mWhat is a WebAssembly component (and why?)
56mKEYNOTE: WebAssembly Update: The Proposals, Wasi, And The Component Model
27mDoes the Component Model Require Extra Copying?