6 ms·

Might be biased/stereotypical, but Rust's cargo does dependencies really well. It's as easy as npm to add new dependencies, but there aren't thousands needed to

Might be biased/stereotypical, but Rust's cargo does dependencies really well. It's as easy as npm to add new dependencies, but there aren't thousands needed to do anything, and if you take a look at your Cargo.lock/`cargo tree` you can really get to know each of them and what they do or why they're pulled in. I'm still bloat-wary, maybe as a leftover from doing webdev, but with less transitive dependencies in the first place you can actually go through and prune things that aren't needed, or open PRs to transitive deps to prune from their trees or update deps to the latest version to deduplicate your tree. (If there are multiple semver-incompatible versions in a dep tree, they just both get compiled in - for most apps though, you should be able to get the number of duplicates to 0 or almost that.)

aprdm 5y ago
I wonder how Cargo will be regarded as in 2-5 years if it gets anywhere near the number of projects/libraries that say Python or Javascript has.
- pjmlp 5y ago
  You can either go to lunch or buy a Threadripper server to be able to compile a full project from scratch, everytime you want to check something. Unless by then cargo has already learned how to deal with binary crates.
colin_mccabe 5y ago
If compile time is the problem, Rust is not (yet?) the solution. I agree that Cargo is much better than the Go build system, though.
- morelisp 5y ago
  coolreader18's points are mostly about the culture of JavaScript vs. Rust (where Go also hews much closer to the Rust side). Setting aside lockfiles vs. MVS (which won't get "solved" in an HN debate), why do you prefer Cargo to go mod?
pjmlp 5y ago
For me, it only gets the "really well" when it also does binary dependencies vcpkg/conan style.
- Nullabillity 5y ago
  Having tried both, focusing on source dependencies is the only way to make sure that dependency sources are universally available and buildable, which makes a huge difference in the long run. Just look at NuGet's issues getting SourceLink adopted. Binary caching á la Nix can work, but I can't really see that working out without Nix's commitment to environment purity.
  - pjmlp 5y ago
    When one is lucky to use server hardware as workstation, and works in domains that don't depend on selling binary libraries for their business.
    - Nullabillity 5y ago
      > When one is lucky to use server hardware as workstation Sounds like something is pretty screwed up if you're running cargo clean as part of your regular workflow. > works in domains that don't depend on selling binary libraries for their business Play stupid games, win stupid prizes? Meh.

aprdm 5y ago

I wonder how Cargo will be regarded as in 2-5 years if it gets anywhere near the number of projects/libraries that say Python or Javascript has.

pjmlp 5y ago
You can either go to lunch or buy a Threadripper server to be able to compile a full project from scratch, everytime you want to check something. Unless by then cargo has already learned how to deal with binary crates.

colin_mccabe 5y ago

If compile time is the problem, Rust is not (yet?) the solution. I agree that Cargo is much better than the Go build system, though.

morelisp 5y ago
coolreader18's points are mostly about the culture of JavaScript vs. Rust (where Go also hews much closer to the Rust side). Setting aside lockfiles vs. MVS (which won't get "solved" in an HN debate), why do you prefer Cargo to go mod?

pjmlp 5y ago

For me, it only gets the "really well" when it also does binary dependencies vcpkg/conan style.

Nullabillity 5y ago
Having tried both, focusing on source dependencies is the only way to make sure that dependency sources are universally available and buildable, which makes a huge difference in the long run. Just look at NuGet's issues getting SourceLink adopted. Binary caching á la Nix can work, but I can't really see that working out without Nix's commitment to environment purity.
- pjmlp 5y ago
  When one is lucky to use server hardware as workstation, and works in domains that don't depend on selling binary libraries for their business.
  - Nullabillity 5y ago
    > When one is lucky to use server hardware as workstation Sounds like something is pretty screwed up if you're running cargo clean as part of your regular workflow. > works in domains that don't depend on selling binary libraries for their business Play stupid games, win stupid prizes? Meh.