For me this is the last nail in the coffin for #Go.

I've never bought much into the language. I've been impressed by its constructs to natively manage and synchronize asynchronous operations, but its rigidity when it comes to programming paradigms (no proper object-oriented and functional constructs in the 21st century, seriously?) means that I see it as a language that seriously limits expressivity, and doomed to generate a lot of boilerplate. It's a language very good at solving the types of problem that are usually solved at Google (build and scale large services that process a lot of stuff in a way that the code looks the same for all the employees), and little more than that.

After #Rust really took off, I didn't see a single reason why someone would pick Go.

And now here we go with the last straw: Google has proposed to embed telemetry collection *into the language toolchain itself*. And, according to Google, it should be enabled by default (opt-out rather than opt-in), because, of course, if they make it an opt-in then not many people will explicitly enable a toggle that shares their source code and their usage of the compiler with one of today's biggest stalkers. If they make it an opt-out, well, many people won't even notice, and you can grab more data points from people, whether they know/like it or not.

If you build open-source projects in Go, it's time to drop it and start considering alternatives. The market for modern compiled language is much more competitive now than it was a decade ago. We knew already that we couldn't trust a programming language developed by the largest surveillance company on the planet.

theregister.com/2023/02/10/goo…

Google's Go may add telemetry that's on by default

Some devs object because they don't trust Mountain View

^{Thomas Claburn (The Register)}