I feel like Rust would be some complaint from the compiler saying that some apparently unrelated struct can’t be Send/Sync for some inscrutable reason. Or something about pinning a future.
I would disagree. Especially since unlike npm every part of cargo was through through with all the experience and knowledge gained from npm, pip, nuget & co.
I have a LOT more problems with npm over cargo. Also it’s 1 tool and not 100 different tools to do the same job (npm, pnpm, yarn, bun, deno, etc…)
Rust: Downloading 7390327 crates…
I feel like Rust would be some complaint from the compiler saying that some apparently unrelated struct can’t be Send/Sync for some inscrutable reason. Or something about pinning a future.
So it’s just JS with an even more immature spec
I would disagree. Especially since unlike npm every part of cargo was through through with all the experience and knowledge gained from npm, pip, nuget & co.
I have a LOT more problems with npm over cargo. Also it’s 1 tool and not 100 different tools to do the same job (npm, pnpm, yarn, bun, deno, etc…)
Rust and Cargo were built to be in a symbiosis with each other.
NPM is an afterthought of a rushed language.
Same with C and C++ libraries.
Definitely not as egregious as with rust though
Yes, but you also don’t get cargo to find C/C++ libraries.
I literally never had more than 10 dependencies for any standalone program (standalone as in not dependent on a whole ecosystem like KDE)