Why you should consider Web Assembly in your next frontend project
summary
WebAssembly runs near‑native code in the browser by compiling languages like Rust to a compact .wasm binary and shipping a glue layer (wasm-bindgen + wasm-pack produces .wasm, .js and .d.ts which can be published to npm); the presenter compiles Rust with the target wasm32-unknown-unknown and demonstrates a working Game of Life demo with interactivity via a toggle_cell JS binding. WebAssembly exposes four primitive types, about 70 built-in ops, shows lower variance and faster runs than JS across Chrome/Firefox/Safari, and can also run server-side via WASI/wasmtime.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:26Web Assembly
- 3:03JavaScript vs WebAssembly
- 6:05WASM example (1)
- 10:43Using cargo
- 12:16How to compile rust programs to wasm
- 12:58Rust example (4)
- 15:58Rust example (5): Use the package
- 16:17Rust example (6)
- 17:20Game of life
- 20:33Code overview: index.html
- 24:54Examples: AutoCAD
- 32:10Pyodide
- 34:01Blazor
related talks
36mWhy you should consider Web Assembly in your next frontend project
36mWhy you should consider Web Assembly
44mWhy you should consider WebAssembly in your next frontend project
16mWhy WebAssembly
50mWeb Assembly
41mCreating High-Performance Web Apps with WebAssembly
22mWebAssembly beyond the browser
41mLet's build with WebAssembly!