You're doing the same thing you're criticising, being dismissive of my concern. > If you don't want to use proxy.golang.org, use goproxy.io Yes, I can do that

You're doing the same thing you're criticising, being dismissive of my concern. > If you don't want to use proxy.golang.org, use goproxy.io Yes, I can do that, but as I mentioned in my original post having to get an entire team of people and fleet of CI systems to use a non-standard configuration which is not communiciable in the project repo is a minor PITA. If and when proxy.golang.org has a bad day, builds will fail. Go developers will have a bad day. Having the ability to work around it doesn't make it not a lynchpin. As for the "FUD about analytics being collected" it was an offhanded quip. I thought it read pretty clearly as not entirely serious hence the prefix "The cynical side of me feels" and not "I feel". It doesn't merit the effort of defending.