Cargo has never frustrated me like npm or pip has. Does Cargo ever get frustrating? Does anyone ever find themselves in dependency hell?

Title. I've spent days in dependency hell with npm and pip.

At my day job, I have many weeks where I apologize for failing to meet my sprint goals because I'm struggling with npm and our internal repos. Too many undocumented moving parts and dependency issues; too much knowledge that lives in the heads of people who had left.

I've never experienced this with cargo. Everything I need to do with Cargo is easy and fast. Building, testing, publishing, adding dependencies, installing tools to my global config, etc.

When I hear a new project is written in Rust, I'm more inclined to check it out, because installing something through NPM is always painful and laborious, but installing/building it through Cargo is dead-easy.

The only time I have ever been frustrated with Cargo is that some commands can take awhile to run, such as builds.

I feel like I want to evangelize Rust just for Cargo alone. I love it. Cargo has never frustrated me or wasted my time.

What I'm wondering is, do I have a blind spot? Is it possible some people hate Cargo the way I do npm? Specifically, I'm wondering:

• Has Cargo ever frustrated you?

• Have you ever been in dependency hell when working on a Rust project?

• Have you ever found it difficult or annoying to publish a crate, to build a project, etc?

I really just want to know if there are some rough edges I haven't hit.