The Unglamorous Side of Rust Web Development
summary
Maintainers of the Code Red web framework catalog concrete pain points: async Rust forces learning two styles (async fn vs manual Future), yields useless backtraces that show application code only between frames 9–10, and lacks async drop and easy pinning; database tooling requires triple-schema bookkeeping in Diesel so Code Red implements declarative, auto-generated migrations; macros and generics bloat binaries (example: 2 → 37 MB) and slow compile times (SQLx macro consumes ~65% of expansion time); hot reloading is experimental and fragmentation persists.
AI-written summary · about
chapters (10)
- 0:00Rust web struggles
- 1:28Built Rust web framework
- 2:29Async Rust pain points
- 6:05Database access challenges
- 10:19Error handling in web apps
- 13:31Macros and generics
- 15:59Slow iteration speed
- 19:29Fragmented web ecosystem
- 21:38Rust vs Python
- 23:44Rust for web development
related talks
01h 00mThe Future of Rust Web Applications
42mBuilding a Web Application with Rust
23mTips for Writing a Web Server and Beyond
27mThe State of Rust Web Frameworks: Pros, Cons & Use Cases
36mFast, secure, safe: the web that can still be
31mBlasting Off with Rocket: A Deep Dive into Rust's Web Framework
25mMy Blog is Hilariously Overengineered to the Point People Think it's a Static Site
07mQ&A with Francesco Ciulla