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.

[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/

Fantastic links, thanks! I like the DNS-based way so much I am still trying to tease apart its disadvantages.

Most DNS registrations won't match the lifetime of the software.

Thank you. I didn’t quite see all that happening but heard echoes of it from time to time, then really jumped in after they adopted modules.

That sounds like a chatgpt prompt lol

Thanks pal. I’m not feeling self-conscious at all now