A little off-topic. I like Go but haven't used it in a while.
While offline I remember a couple go command operations were surprisingly giving me proxy.golang.org or network unavailable errors. In the sense that it had no reason to touch the network. Can you refresh my memory what they were? Or if they are still present? I can't for the life of me find or remember the answer.
It was what made me discover some of the things the article mentions, like the package index.
If you download a package that supports go mod and try to build it, it'll automatically try to fetch dependencies through proxy.golang.org
You can override the proxy, and there are open source implementations of the module datastore[1], but it's not made clear front and centre to the end user that building software will call a Google owned service.
It was a source of contention for some when the default toolchain moved in this direction.[2]
While offline I remember a couple go command operations were surprisingly giving me proxy.golang.org or network unavailable errors. In the sense that it had no reason to touch the network. Can you refresh my memory what they were? Or if they are still present? I can't for the life of me find or remember the answer.
It was what made me discover some of the things the article mentions, like the package index.