The Future of Rust Web Applications
summary
Claims Rust can run full-stack web UIs with real tooling: uses Leptos, Dioxus, Sycamore plus wasm-bindgen and web-sys; demos show hot-reload hacks and even inplace binary patching prototypes to avoid full recompiles. Concrete costs and wins appear: single-page islands drop client wasm to around 44 KB or 43 KB; a monolithic build hits ~235–256 KB and shows ~2.2s load, lazy-loading chunks (~22 KB) trims initial payload and keeps interactions fast.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:48Talk overview
- 2:05Rust on the web scope
- 4:20The history of the web
- 6:46Evolution of web architecture
- 10:45WebAssembly introduction
- 13:06Why use Rust
- 15:31Rust web frameworks
- 19:30Current capabilities
- 20:52Current limitations
- 21:35Addressing compile times
- 27:27Addressing binary sizes
- 31:00Islands architecture
- 34:27Islands demo
- 36:40Advanced routing
- 38:27Code splitting demo
- 45:36Ecosystem and future
- 47:11Q&A
related talks
36mWeb development with Rust, is it ready? Is it even useful?
25mThink About Front-end Web Development with Rust
27mThe State of Rust Web Frameworks: Pros, Cons & Use Cases
24m"Web Sites, Web Apps, and Web Assembly"
34mMake Web UI Easy with Leptos
38mRust on the frontend
25mWTF, Rust for Web Development??
47mRewrite the web with Rust and Web Assembly