Explore · People

People

Writers, crate authors, and educators whose output is worth following to understand how Rust thinks and where it is going. Not exhaustive — opinionated.

David Tolnay@dtolnay

Author of serde, syn, anyhow, thiserror, and proc-macro2 — the crates that most production Rust depends on. His four published essays cover async pitfalls, reference mental models, soundness bugs in safe code, and scaling open source triage.

Andrew Gallant@BurntSushi

Author of ripgrep, regex, csv, and memchr. Writes with unusual depth on performance, correctness, Unicode handling, and the real tradeoffs in systems programming.

Aleksei Kladov@matklad

Architect of rust-analyzer. Writes precisely on compiler internals, software architecture, and language tooling. His posts on salsa and incremental computation are required reading for anyone building language tools.

Saoirse Rooney@withoutboats

Proposed and co-designed async/await for Rust. Her writing on Pin, Waker, the polling model, and language design is essential for understanding async Rust at a conceptual level.

Niko Matsakis@nikomatsakis

Lead designer of Rust's ownership and borrow-checking system. Blogs at Babysteps with rare candor about language design decisions, the limits of NLL, and the direction of the type system.

Jon Gjengset@jonhoo

Author of Rust for Rustaceans and the Crust of Rust video series. Exceptionally skilled at explaining Rust internals — atomics, channels, lifetime variance — to developers who already know the basics.

Steve Klabnik@steveklabnik

Co-author of The Rust Programming Language. Shaped how the Rust community explains the language to newcomers. Writes on programming languages, community dynamics, and software history.

Carol Nichols@carols10cents

Co-author of The Rust Programming Language and co-founder of Integer 32. Helped establish the editorial standards and pedagogical approach that makes the Rust Book unusually good.