Improving web app with Rust and WASM
summary
Comparison shows Rust+WebAssembly replacing hot JavaScript paths in a React + three.js app, using wasm-bindgen and wasm-pack with webpack to build npm modules. Benchmarks use arrays of about 60,000 input values and ~30,000 outputs; raw compute is small (≈2 ms) but data marshaling costs roughly 20% transfer overhead. Typical speedup is ~1.3× in production builds, spikes to ~6× in some dev/Edge runs. End result: selection and collision code moves to Wasm, reducing GC pauses and improving frame budgets.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:50Webassembly
- 9:46Performance
- 16:48Outcomes
- 19:303d Collisions
- 26:16Std Web Draw Script Bindings
- 28:10Debugging Webassembly
related talks
44mOut of the JavaScript Box: Front-End Rust Programming
43mDo things blazingly fast with WebAssembly
22mExtending JavaScript with Rust
47mRewrite the web with Rust and Web Assembly
33mWebpack + WebAssembly the future
20mUsing Rust and WASM
41mLet's build with WebAssembly!
44mWhy you should consider WebAssembly in your next frontend project