Why cargo Ruined Every Other Package Manager for Me

I came to Rust for the memory safety and stayed for cargo. That's not a joke. The language is excellent, but the tool that wraps it is the thing I miss the second I context-switch into any other ecosystem.

One command, no ceremony

Starting a project is the entire onboarding experience, and Rust nails it:

cargo new yap-experiment
cd yap-experiment
cargo run

No virtualenv to activate, no lockfile-vs-manifest confusion, no "which of the four tools is canonical this year." The manifest is Cargo.toml, the lockfile is Cargo.lock, and both do exactly what their names say.

The parts I didn't know I needed

• cargo fmt — formatting is not a personality trait, it's a solved problem.
• cargo clippy — a linter that teaches you the language while it scolds you.
• cargo test — tests live next to the code, in the same file, and just run.
• cargo doc --open — your dependencies' docs, generated locally, offline.

A build tool should be boring. cargo is gloriously, reliably boring, and after years of YAML archaeology that feels like a spa day.

The real lesson

Good tooling is a moral position: it says the maintainers respect your time. Every hour cargo saves me is an hour I spend on the actual problem instead of the meta-problem of getting the computer ready to work. That's the whole game.