Why you should consider WebAssembly in your next frontend project
summary
Argues that WebAssembly gives near‑native speed and lets backend code be reused in the browser, showing a Rust workflow that compiles with wasm-pack and generates glue with wasm-bindgen into an npm package; demos include a working Game of Life built in Rust → wasm and used from TypeScript, and benchmarks that show tighter performance spread than JavaScript; notes serverless runtimes with cold starts: Node ~200 ms, Fastly ~35 μs, Cloudflare ~5 ms.
AI-written summary · about
chapters (21)
- 0:00Start
- 1:03Agenda
- 2:01About Myself
- 2:51Webassembly
- 3:57Contrast the Javascript with Webassembly
- 10:27Code Explorer
- 11:08Rust
- 11:25Background about Rust
- 15:21Dependencies
- 17:21Typescript File
- 19:11Game of Life
- 22:36Performance
- 24:43Digital Signal Processing Library
- 25:35Autocad
- 26:13Autocad Flash App
- 28:02Future Plans for Web Assembly
- 28:47Serverless Webassembly
- 30:05Serverless Web Assembly
- 31:30The Web Assembly System Interface
- 35:03Assembly Script
- 40:21Conclusion
related talks
36mWhy you should consider Web Assembly in your next frontend project
43mWhy you should consider Web Assembly in your next frontend project
36mWhy you should consider Web Assembly
43mDo things blazingly fast with WebAssembly
41mCreating High-Performance Web Apps with WebAssembly
41mLet's build with WebAssembly!
37mBuilding a better web with WebAssembly at the edge
30mImproving web app with Rust and WASM
