News for hackers. Stuff that matters.
Re:Pip and cargo are not the same by dirkg on Thursday January 26, 2023 @12:57AM (#34528152)
Nodejs solved all this years ago, now we have super fast shared package managers like pnpm, yarn etc, not to mention deno etc, why can't other languages adopt the same system?
Re:Pip and cargo are not the same by Yoric on Thursday January 26, 2023 @01:52AM (#34528479)
I assume that it is harder for Rust, because it needs to deal with `features`, with cross-compilation, with the developer using `nightly` for some projects, `stable` for others, pinned versions for yet others, etc.

That being said, harder doesn't mean unsolvable.

Re:Pip and cargo are not the same by pjmlp on Thursday January 26, 2023 @03:03AM (#34528996)
Maven and CPAN did it first, and in many ways better than node.
Re:Pip and cargo are not the same by pxc on Thursday January 26, 2023 @10:54AM (#34533313)
Node supports circular dependencies and arbitrary pre/post-install scripts, which are both disasters for downstream packaging. Node is not a model here.

The CAS that gets symlinked into vendorized directories à la pnpm is the Nix model, which is indeed an improvement that other package managers which support vendorization should incorporate.