WebAssembly: the browser is now a real virtual machine
summary
WebAssembly turns browsers into a true stack-based virtual machine executing near‑native code by compiling modules in a streaming two-pass process and reusing JIT infrastructure. It exposes a linear memory model (64 KiB pages) with only four primitive types today, so strings require explicit memory copies; toolchains include LLVM for frontend compilation and Rust + wasm-bindgen + cargo (packaged via wasm-pack -> npm) to produce and publish modules. A concrete example shows a pixel‑colorization app running much faster after moving heavy loops into wasm, and multithreading, GC and richer types are planned for the future.
AI-written summary · about
chapters (11)
- 0:00WebAssembly in browsers
- 3:54Origins and early uses
- 7:47WebAssembly as VM
- 12:40WebAssembly internals
- 17:35JS engines and WebAssembly
- 22:16Rust and compatible languages
- 26:52WebAssembly today
- 33:21Shared memory with JS
- 37:13Tools and libraries
- 40:26WebAssembly roadmap
- 42:14WebAssembly in modern apps
related talks
45mWebAssembly: Browser is now a real virtual machine
35mWebAssembly: now web is a new compiler target architecture
44mWebAssembly
42mWebAssembly: A New Compilation Target for the Web
25mWebAssembly: Binary in Plain English
17mA case for Web Assembly
53mWebAssembly – To the browser and beyond!
16mWhy WebAssembly