Why WebAssembly
summary
Explains that WebAssembly runs compiled binaries in browsers alongside JavaScript, showing a workflow: compile Rust or C/C++ via LLVM toolchains into a .wasm plus JS glue and HTML, load in Chrome/Firefox, and call functions from JS. Gives concrete wins: image filters run 200–2000× faster, some edit paths see 300× improvements. Mentions binary .wasm and text WAT format, WebGL/audio/service workers compatibility, and practical migration of legacy C/C++ code without full rewrites.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:26JavaScript limitations
- 2:15JavaScript performance limits
- 5:05What is WebAssembly
- 8:14WebAssembly in browsers
- 9:19WebAssembly from languages
- 11:10WebAssembly with JavaScript
- 11:31WebAssembly applications
- 14:44WebAssembly future
related talks
25mWebAssembly: Binary in Plain English
42mWebAssembly? Web and Assembler? WTF!
52mWebAssembly vs JavaScript
23mWebAssembly for the rest of us
27mHow WebAssembly is changing the Web and what it means for you
35mWebAssembly: now web is a new compiler target architecture
44mWebAssembly
36mPractical WebAssembly
