> I don't think it's fair to describe the Go proxy as "calls home"; no one says that about Rubygems, PyPI, npm, or any other package tool.
The Go equivalent of `gem`, `pip`, `npm`, `apt`, `cargo`, etc, is `go get`. There's no issue with `go get` connecting to internet.
On the other hand, `go build`, `ruby`, `python`, `node`, `gcc`, `rustc`, have no business doing anything that requires the network (obviously `node` etc are interpreters, so the user's program could have networking code, but that's the user's code, and not the interpreter's code).
So, `go get` using Google's proxy by default, fine, this is Google's tooling, we can just avoid using `go get`.
But the problem is that this proxy sneakily creeps into the `go build` command as well, so you can't just "not use `go get`" because you have to set flags for the compiler as well.