8 engineers on Hacker News describe using Cargo first-hand: 3 endorse it, 2 regret it, 1 are mixed.
“it was extremely painful 5 years ago when cargo didn't properly do feature unification separately for build dependencies vs. target dependencies.”
regret · production · osiris88 · 2025-12-28 · source ↗ · wrong label?“cargo check and the cargo package system make it very easy for LLMs to check their work”
endorse · personal · 2.5 yr · hadlock · 2025-12-09 · source ↗ · wrong label?“Cargo is much easier to use than cmake, make, and other custom build scripts we were using before.”
endorse · production · 3 yr · thesuperbigfrog · 2024-12-13 · source ↗ · wrong label?“cargo encourages bad habits. IMO Dependencies should be avoided by default”
regret · production · grayhatter · 2024-12-13 · source ↗ · wrong label?“It's a reasonable choice on Cargo's part but yes, our team has learned to be very conservative to diffs on `Cargo.lock`”
mixed · production · cropcirclbureau · 2024-08-01 · source ↗ · wrong label?“the package manager exists (and is good)”
endorse · personal · cylon13 · 2020-12-21 · source ↗ · wrong label?“eventually we switched to using Cargo's experimental support for artifact dependencies”
neutral · production · kibwen · 2023-07-19 · source ↗ · wrong label?“using Rust for work now, so running cargo instead of make”
neutral · production · toast0 · 2022-12-15 · source ↗ · wrong label?