JavaScript Won the Web, Rust Is Taking the Critical Path
summary
Argues that JavaScript stays dominant for UIs while Rust moves onto the real bottlenecks: latency, memory, safety, and predictability. Cites Cloudflare’s Pingora proxy handling over 1 trillion requests per day at one third the CPU and memory, Discord’s Rust rewrite to eliminate GC latency spikes for read states, Shopify using WebAssembly sandboxes, and compile-time DB checks with SQLx. Describes the runtime model with Tokio, where futures are polled and resumed, and recommends a hybrid TypeScript frontend plus Rust core for critical paths.
AI-written summary · about
chapters (17)
- 0:00Introduction & A Rust Talk at CascadiaJS
- 1:41JavaScript Won the Web
- 3:04When Web Development Becomes Infrastructure
- 5:34The Modern Web Stack Has Different Priorities
- 6:33Why Rust Excels on the Critical Path
- 8:35Cloudflare's Pingora: Rust at Massive Scale
- 9:35Discord's Rewrite for Predictable Latency
- 10:59Shopify, WebAssembly, and Safe Sandboxes
- 12:14The Rust Web Stack Explained
- 14:18Tokio and Rust's Async Runtime
- 15:59How a Rust Web Request Flows
- 16:47SQLx and Compile-Time Database Validation
- 18:07Where Rust Wins (and Where It Doesn't)
- 19:35The Real Cost of Adopting Rust
- 20:24Rust vs JavaScript, Go, and Java
- 22:07A Practical Hybrid Architecture
- 24:46Rust Owns the Critical Path
related talks
25mWTF, Rust for Web Development??
27mThe State of Rust Web Frameworks: Pros, Cons & Use Cases
01h 00mThe Future of Rust Web Applications
30mRust in the Browser for Javascripters:New Frontiers,New Possibilities
45mSustainability with Rust
25mThink About Front-end Web Development with Rust
56mWhen to Choose Rust
36mWeb development with Rust, is it ready? Is it even useful?