The Rust Rewrite Debate: When It Is Worth It, and When It Is Not

Every few months a high-profile project announces it is rewriting a component in Rust, and the discourse reliably splits into cheerleaders and skeptics. Both camps have a point.

The case for Rust

Memory safety without a garbage collector is a genuine advantage for systems software, and the tooling around cargo and the crate ecosystem is excellent.

The case against a rewrite

A rewrite throws away years of hard-won bug fixes encoded in the existing code. The second-system effect is real, and the new version often ships with fresh bugs the old one had already solved.

The best rewrites are incremental. Replace one component at a time, behind a stable interface, and keep the old system running until the new one earns trust.

A practical heuristic

Rewrite in Rust when memory safety or performance is a core requirement you cannot meet otherwise, and when you can do it incrementally. Avoid it when you are chasing novelty or resume-driven development.