Fast, secure, safe: the web that can still be
summary
Claims that switching from dynamic languages to Rust cuts bugs and server count with concrete examples: Twitter expects ~10x throughput from replacing Ruby with Scala and measures ~50x; NewsBlur runs ~52 servers where Rust would need one or two; test suites commonly take 7–20 minutes; a Rust prototype is about a minute faster in a synthetic case. Shows a Rust HTTP header library (tp myhttp) that encodes headers as enums to eliminate injection and parsing classes of bugs, and cites Skylight/New Relic agents written in Rust.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:44The mess we're in
- 1:32Subject matter
- 7:01Performance
- 11:12What is it doing in that time?
- 12:54Who is saved time?
- 17:05Case study: HTTP headers
- 17:32Example: DNT header
- 22:55The really good part?
- 24:02Ur/Web
related talks
01h 00mThe Future of Rust Web Applications
27mThe State of Rust Web Frameworks: Pros, Cons & Use Cases
04m"Scaling Safety: Rust at Google”
39mFearless Security with Rust
42mBuilding a Web Application with Rust
07mQ&A with Francesco Ciulla
35mrustls: modern, faster, safer TLS
25mThe Unglamorous Side of Rust Web Development