Map rendering using WebGPU and WASM
summary
A cross‑platform map renderer exists, written in Rust and compiled to WASM, using WebGPU via the Rust implementation wgpu, and now officially supported by MapLibre. It turns vector tiles into GPU triangles (tessellation is the costly step) and moves that work into WebAssembly threads with shared memory, yielding large speedups over TypeScript. It runs in browsers and native on desktop and mobile, achieves near pixel‑perfect parity, and notes that full multi‑threaded WebGPU is not yet finalized.
AI-written summary · about
chapters (13)
- 0:00Vector map rendering intro
- 1:48Speaker background
- 3:11Tile-based rendering basics
- 6:04Portable map rendering challenges
- 7:51MapLibre and limitations
- 9:16WebGPU for portability
- 12:50WebGPU features for maps
- 13:54WASM and multi-threading
- 16:30Pitfalls and compatibility of WebAssembly
- 18:18Rust, WebGPU, WASM fit
- 19:42Rust benefits for maps
- 21:28Future plans
- 22:32Conclusion
related talks
30mWasi-Webgpu: Build Beautiful Graphics and Safely Run AI with Any GPU
31mGPUs Unleashed! Make Your Games More Powerful With wasi-gfx
27mWebAssembly for Performant Interactivity
30mImproving web app with Rust and WASM
25mPathfinder to GPU Offload in WASM
47mRewrite the web with Rust and Web Assembly
31mUnlocking the Potential of Reusable Code with WebAssembly
02h 13m2D Graph scene in Rust