Rust and WebAssembly threads on production: a field report

on YouTube ↗10m

" summary

A Node.js‑like runtime called WebContainers runs entirely in the browser by mapping processes to web workers, using shared memory and WebAssembly threads for performance, and relying on Rust for low‑level components; this is deployed in production and mostly works. Networking leverages service workers and async executors to interact with the browser event loop. Remaining pain points include missing GC, browser/runtime bugs, and some tooling limitations that the team reports and patches.

AI-written summary · about

" chapters (10)

1. 0:00Introduction
2. 0:44StackBlitz and online IDEs
3. 2:29Playgrounds vs remote dev
4. 3:57Web Containers strengths
5. 4:37POSIX in browser feasibility
6. 6:02Practicality over raw tech
7. 7:32Rust and Wasm for performance
8. 8:57Challenges and stress testing
9. 9:40Wasm improvements wish list
10. 10:03Closing and call to action

" related talks

• 25mThink About Front-end Web Development with RustYosuke Onoue · RustFest Global 2020
• 45mWebAssembly: Browser is now a real virtual machineMatthias Dugué · JSDay 2019
• 40mRust, WebAssembly, and the future of ServerlessSteve Klabnik · Full Stack Fest 2019
• 46mA State Of WebAssembly - The Browser is now a real VMMatthias Dugué · GrillJS 2019
• 38mWebAssembly beyond the browserMete Atamel · Voxxed Days Thessaloniki 2023
• 41mCreating High-Performance Web Apps with WebAssemblyKonstantin Möllers · DevDays Europe 2019
• 30mRust in the Browser for Javascripters:New Frontiers,New PossibilitiesSean Grove · ReactiveConf 2019
• 24m"Web Sites, Web Apps, and Web Assembly"Chris Biscardi · RustConf 2024