What does it even mean for it to be "supported for years to come"? It's not a web service.
And it's usually problems people are solving are work that instigate most of these contributions, so it's a damn good thing Go has a company like Google to act as steward, regardless of all the useless FUD people like to pretend "may" happen because they can think it up.
At least that is how it reads.
So you don't get to be angry that the things open source projects need - strong cores - usually come in the way of companies paying for them.
Go having Google is a good thing, regardless of all the pointless stupid FUD people like to spread because it makes them feel better to point out something that could be scary.
Your arguments are deeply cargo cult-ish: they lack any rational train of thought and boil down to an empty belief on how a greater power will eventuall deliver good things to those who have faith in it.
What does that even mean? It's such a ridiculous statement, don't even know where to begin.
> they lack any rational train
Care to back this up with facts rather than slinging mud?
It makes sense if you think about it: how many companies adopted Go because they saw that it had Google's name on it?
Even if you don't mind if the language itself stops evolving you still need somebody to maintain it. I'm fine coding in C99 without the features of newer standards but if I can't find a C compiler that can efficiently target modern architectures I have a problem.
That being said, Go is mainstream enough that, if Google EOLs it, the community will pick up the torch. Simias says its harder for Go than, say, Rust. It probably is.
I'm pretty sure those writing and building software today would like it to build and run 6 months from now.