A State Of WebAssembly - The Browser is now a real VM
summary
Demo compiles Rust via Rust + LLVM into WebAssembly, uses wasm-pack/wasm-bindgen to wire Rust functions and JS APIs, and implements a simple blockchain miner to compare throughput: JavaScript runs ~340 rounds in 8s (~26 ms/round) while the WASM build hits 912 rounds in 10s (~12 ms/round). Shows linear memory and string-by-pointer plumbing, notes only four primitive WASM types, current single-thread limits (web workers workaround), and upcoming streaming compile and multithreading.
AI-written summary · about
chapters (14)
- 0:00Introduction to WebAssembly
- 3:07History of JavaScript evolution
- 7:10What is WebAssembly
- 10:01Stack-based vs register-based VMs
- 13:54WebAssembly and JavaScript engines
- 16:00Why Rust for WebAssembly
- 18:31Running WebAssembly in browsers
- 21:29Linear memory in WebAssembly
- 24:23Wasm-bindgen and tooling
- 28:22WebAssembly in blockchain demo
- 34:25Current WebAssembly status
- 36:35WebAssembly security features
- 38:46Future of WebAssembly
- 39:29Conclusion and Q&A
related talks
45mWebAssembly: Browser is now a real virtual machine
43mDo things blazingly fast with WebAssembly
41mLet's build with WebAssembly!
44mWebAssembly: the browser is now a real virtual machine
22mThe state of WebAssembly
23mWebAssembly for the rest of us
47mRewrite the web with Rust and Web Assembly
33mWebpack + WebAssembly the future