Maybe if Reader were written in Go, it wouldn't have been killed.
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.