Rust in Action

Most introductory Rust books teach the language and let you infer the systems-programming payoff later. Rust in Action inverts that: every chapter is anchored to a concrete, runnable systems project — a CPU emulator, a file-format parser, a simplified TCP/IP implementation, a key-value store with its own on-disk format — and the language features get introduced as they’re needed to build the thing in front of you.

That project-first structure is the book’s real strength. Chapters on memory (how Rust’s ownership model maps onto the stack and heap), on bit-level manipulation, and on writing a minimal network stack give you a much more visceral sense of what Rust buys you over a garbage-collected language than an abstract discussion of the borrow checker ever could. The chapter on time and timekeeping — a genuinely hard, underserved corner of systems programming — is unusually good and rarely covered elsewhere.

Where it’s weaker: because each chapter is built around a specific project, the language coverage is less systematic than a reference-style book — you’ll pick up traits and generics somewhat incidentally rather than in one dedicated treatment. It also assumes you’re comfortable reading unfamiliar, project-specific code without much syntax hand-holding, so it’s a poor choice as a true first Rust book.

Compared to Programming Rust: Blandy et al.’s book explains systems concepts and then shows examples; McNamara’s book builds systems and explains concepts along the way. Pick this one if you’d rather learn Rust by shipping a working TCP stack than by reading a chapter about one.