News for hackers. Stuff that matters.
Re:Go at Digital Ocean by saghm on Sunday November 05, 2017 @03:22PM (#15631358)
> it's a better system imo than a centralized package manager like pypi / rubygem where names need to be unique

I'll have to disagree there; while having namespaced packages gives some advantages, having a centralized repository gives you things like proper versioning, which is worth all the terrible package names in the world to me.

Re:Go at Digital Ocean by carussell on Sunday November 05, 2017 @04:07PM (#15631560)
A central repository doesn't automatically give you versioning, and URLs as package IDs doesn't take it away. These are orthogonal issues. It just happens that Go has chosen an approach for now that results in a lot of pain.
Re:Go at Digital Ocean by saghm on Sunday November 05, 2017 @04:11PM (#15631584)
I don't think they're completely orthogonal; I think it's much easier to enforce versioning with a central repository than URLs as package IDs. It's not a coincidence that the most common centralized package managers (e.g. Ruby, Python, NodeJS, Rust, Linux distro package managers, and brew) all enforce versioning and things like Go and Vim packaging don't.
Re:Go at Digital Ocean by weberc2 on Sunday November 05, 2017 @04:22PM (#15631671)
Go and vim don't have "distributed package managers"; they just punt on package management altogether. The next step up from that is a centralized package management system, and if you care that much you'll probably build in some notion of versions (even if they're nondeterministic or otherwise broken, as in the case of pip, npm, and many Linux package managers). Building a distributed package manager is quite a lot more work.