netstack.fm Hyper With Sean McArthur (Ep 2 Remastered)
Mar 3, 2026
Sean McArthur, creator of the Hyper ecosystem and author of the Warp framework, is a systems and Rust engineer focused on HTTP, async I/O, and networking. He recounts Hyper’s origins at Mozilla and its evolution alongside Rust and Tokio. The conversation covers Hyper’s design choices, Warp’s type-driven routing, and the technical challenges of adding HTTP/3 and QUIC support.
AI Snips
Chapters
Transcript
Episode notes
Keeping Hyper Runtime Agnostic
- Hyper deliberately stayed runtime-agnostic so people can use different async runtimes, not just Tokio.
- Hyper 1.0 effort removed Tokio-specific parts and standardized IO traits to make the core portable across runtimes.
Split Higher Level Features Into Experimental Crates
- Split unstable higher-level features into separate crates to reach a stable core faster.
- Sean moved pooling, DNS, and higher-level client code into hyper-util during Hyper 1.0 to stabilize the connection core.
Why HTTP Types Live Outside Hyper
- The http and headers crates were split from Hyper to let other implementations and frameworks share types without depending on Hyper.
- Headers remained hard to stabilize due to many nuanced and potentially breaking typed-header choices.