I think this is a fairly misguided rant, and ignores the real priorities (and risks) that I have as a developer - both personally and professionally. I'm happy to use languages funded by corporations - the incentives for them are clear, they fund development and work on the tooling and spec for their own use-case - they garner additional support, momentum, and goodwill by releasing the language under an open definiti…
> particularly malicious... not any more than I would find it both reasonable and sane for a store to be tracking how many customers they get a day, and to pay attention to what their hot-selling items are. This is substantially less than what code running on your machine can do, which is basically unlimited its spying capabilities. Yes, this is a problem in itself that needs to be fixed. Otherwise you appear to will…
So make your own Go compiler & package manager and stop complaining? The language spec is open.
Or if putting your money where your mouth is feels too hard...
Use an implementation of a corporate sponsored language that has free and open tooling around it... ex: GNU C/G++
Or fuck it - use the GCCGO compiler... https://go.dev/doc/install/gccgo
Because it turns out if this really is your priority - there are active ways to handle it because, despite being corporate sponsored, the language definition is still open...