By stuck you mean Go devs made the sensible decision to have only one, zero configuration, ultra low latency, Garbage Collector that suits Go's common use cases instead of trying to be jack of all trades having many GC's each with their pletora of knobs to adjust.

This is not a sensible decision, it is an idealistic one, and Go will backtrack on it if it lives long enough. People have different use cases, and they will be more than willing to turn a few knobs if it saves them millions of dollars.

It means that golang is relegated to simple server side tools, and not suited for a broader range of programs like the JVM is.

Yep. Go has a focus.

That's how you get from zero to heavy usage in companies like Uber, Twitter, Cloudflare, BBC, Basecamp, Canonical etc... in less than a decade.

The same kind of companies that were all hyped up on Ruby on Rails, and then moved to Java when performance mattered.

Hype driven development is a thing.

Given a large enough sample size, there will always be companies which ditched technology X for Y.

Unless technology X is irrelevantant.

You'd be surprised at the extent hype influences decision making when it comes to choosing which language to use (even in companies you mentioned), at a significant cost down the line. I'll just say I know people at one of the companies you mentioned, and the amount of friction and cost due to them using golang is quite remarkable.

No offense but I'd rather trust the engineers of all these companies combined over an anecdote on the internet.

Not to mention technology change always generate friction. You just can't please everyone.

Assuming those engineers were making sound decisions and not pimping up the CVs at employers' expense.

Exactly what happened at the company I'm talking about.