[jbreckmckye]

It also means that everything is (over) optimised for Google's usecases, but not general purpose applications

I came across this problem pretty directly a couple of weeks ago - I wanted to see if I could port a small C program to Go, where one of the needs is to create gzip archives. But the Go stdlib insists on extraneous padding that breaks the backwards compatibility requirements of my program.

The padding isn't needed, it isn't useful, and you can't opt out of it. So the whole program went in the bin and I have resumed maintaining it in C

This is one of dozens of situations I've experienced where Go's allegedly pristine stdlib design has kicked me in the nuts

[bborud]

How is this «optimized for Google»?

[jbreckmckye]

Somebody at Google decided this is how they wanted it to work. They don't have to explain why and they don't have to fix this deficiency until it becomes a problem for Google

[bborud]

It seems the problem here is that they didn’t “fix” whatever you thought was “broken” and you are upset. And somehow you extrapolated that to mean that Go only follows Google’s needs.

Be a bit more precise. What exactly are you talking about and and what do you think Go does wrong and why have they chosen to do it that way?

[jbreckmckye]

Your tone seems hostile. I'm not obliged to answer you.