News for hackers. Stuff that matters.
Re:Ask HN: Why does every package+module system become a Rub... by dboreham on Monday January 30, 2023 @10:09AM (#34580538)
Go and Rust don't have packages. They have tooling to pull library code from git and build it in-place to be linked into a local project. That's not (really) packaging.
Re:Ask HN: Why does every package+module system become a Rub... by steveklabnik on Monday January 30, 2023 @10:35AM (#34581008)
Cargo does not “pull library code from git” unless you expressly ask for it to.

And given that packages have to depend on other packages, and cannot depend on a git repository, that feature is mostly useful for testing bug fixes, private repos for leaf packages, stuff like that.

Re:Ask HN: Why does every package+module system become a Rub... by tremon on Monday January 30, 2023 @05:59PM (#34587871)
I thought Rust doesn't have binary libraries? If you declare a Rust dependency, cargo pulls its source and builds it together with your own code? I assume that's what the GP meant, anyway.
Re:Ask HN: Why does every package+module system become a Rub... by steveklabnik on Monday January 30, 2023 @06:17PM (#34588089)
Source code is stored in an S3 bucket owned by crates.io, and not from any form of source control, including git.

That the entire code of all dependencies is hosted in one place is an important differentiator of crates.io vs what Go does, which is why this is relevant in this context. Crates.io is centralized, with all of the advantages and disadvantages that that brings, and Go is decentralized, with all of the advantages and disadvantages that brings.