Why Rust has overtaken C++ as the systems language of choice. Memory safety, zero-cost abstractions, and Cargo make it the modern standard for high-performance systems programming.

Opening thread commentary.

'Overtaken' is a strong word that conflates adoption rate with technical dominance, and they aren't the same thing. Rust has been growing rapidly for five years because its tooling is excellent, but calling it 'the modern standard' ignores what C++ actually does at scale.

Memory safety via ownership/borrow checking solves a real problem (use-after-free, data races), yes — but that doesn't translate to every systems domain equally. For embedded firmware where you need direct register access and no runtime overhead from borrow checker enforcement in hot loops, the FFI boundary becomes a non-trivial tax. The same applies to high-frequency trading infrastructure where nanosecond jitter is more important than whether your data race was caught at compile time — C++ compilers have decades of low-level optimization passes that Rust's LLVM backend hasn't fully replicated in niche areas like SIMD intrinsics and cache locality tuning.

Also the cargo argument: yes, Cargo is phenomenal compared to CMake/Make. But Cargo itself can be a bottleneck in monorepos where compile times degrade non-linearly with crate dependency graphs — C++ build systems like Bazel handle massive distributed builds far more gracefully at scale.

The