Re:Ask HN: Why does every package+module system become a Rub...
by pjmlp on Monday January 30, 2023 @09:53AM
(#34580287)
First they weren't supported, so the community created various ways of dealing it including a kind of Google's blessed implementation, then Google decided to create their own official way, then there was the transition time which I guess not everyone has done, having SCM urls as imports is just bad, and how GOPROXY DoS some SCM repos outside of Github.
[ Parent
| on HN ]
Re:Ask HN: Why does every package+module system become a Rub...
by Nzen on Monday January 30, 2023 @11:12AM
(#34581682)
[0] https://go.dev/blog/appengine-gopath gopath / workspaces original
[1] https://go.dev/blog/migrating-to-go-modules current system
[2] https://news.ycombinator.com/item?id=34310674 goproxy agressively polling sourcehut
It's worth recognizing that go isn't alone in dns-based namespacing : java's maven/gradle use the same strategy: https://repo1.maven.org/maven2/gov/nih/imagej/imagej/1.47/
Re:Ask HN: Why does every package+module system become a Rub...
by tomcam on Monday January 30, 2023 @12:29PM
(#34583215)
Fantastic links, thanks! I like the DNS-based way so much I am still trying to tease apart its disadvantages.