4 ms·
I have been using Go for almost a decade now, and this is the second time they crossed a line I think they shouldn't have. The first time was when they introdu
by quectophoton 4y ago
I have been using Go for almost a decade now, and this is the second time they crossed a line I think they shouldn't have.
The first time was when they introduced the GOPROXY and such. Now `go build` suddenly connects to internet by default, sending package names to Google, unless I explicitly opt-out.
As convenient as it seems to be, I would expect a compiler to not even require network connectivity, and fail loudly if something is missing. It should tell me to download the missing packages myself ("run `go get`" or something), not try to automatically fetch them for me. That's not a compiler's job.
I like Go-the-language, and I'm willing to overlook some inconveniences because I accept the trade-offs, but with this I'll try hard to stop using Go at all unless an alternative working compiler (not gccgo) appears.