Maybe I mis-read it, but that comment comes across as a little sarcastic. Hope I'm wrong.
One is a database load balancer (in YT), not the most essential or irreplaceable piece of infrastructure (ie. they can write it in another language whenever they want if the need arises without messing other stuff)
and the other is a services that was not updated anymore, and was left to die, before someone from the Go team asked and re-wrote it in Go. It's not even the full download service, just a part of it IIRC.
Maybe if Reader were written in Go, it wouldn't have been killed.
Sure is a point in Go's favor. It means it can be used to solve an actual problem in a large company.
But what I'm saying is it's not that big of a deal as it may seem to some: it's not like they used Go in some highly critical for them infrastructure or important new project.
On the contrary: they used it at so low a priority project, that it was abandoned and left to rot before somebody volunteered (was not even asked!) to do the rewrite.
(And, no, it was not abandoned because it's C++ codebase meant it could not be fixed -- after all it could be redone from scratch in C++ or Java, as it was redone from scratch in Go. It was merely due to neglect).
So, my point it, this story is not a "investing internally in the language big time" thing, but rather baby steps.