Keep the language working on newer devices, update the compiler, expose new features of the hardware etc...
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.
I never implied otherwise, I merely answered the parent's question. It's worth noting however that Go's maintenance burden is higher than many other languages which are often a layer atop existing infrastructure (Clojure with Java, Rust with LLVM for instance). AFAIK Go devs write maintain the entire toolchain, including a custom linker for instance.
Who takes this kind of argument seriously? The Go community can't support Go without Google because only a company like Google can maintain a linker? You're reaching.
I don't read the comment like that. The original comment invalidates the premise "Go will be maintained in the future, because it is backed by Google". Given how fragile Google's support for non-core projects is, I wouldn't bet on very long term support by Google.
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.
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.