...but you've got to admit: look at the graph. That's an exponential increase in people using go to access the service.
If you're a service based company you can't just ignore the people who use your service.
If people are using go? Provide a go library.
If you see an exponential curve of people accessing it using lua, write a lua library.
It's pretty obviously the right thing for them to do.
Missing generics is not a major problem. Yes, it means you can't write a generic red black tree in the language that doesn't require type-casting. However, for real software solving real problems, you don't often actually need generics. I work on Juju, which is a couple hundred thousand lines of code, consisting of a client and networked servers deployed across an arbitrary number of machines in the cloud. The number of times we might have wanted to use generics in the codebase is approximately 2... and only one of those pieces of code is actually used by more than one type.
Sure, some software really benefits from generics. But most of the time, generics just complicate the code with little to no benefit. Many things people do with generics can be accomplished with interfaces and just writing code that has fewer assumptions about the outside world.
The majority of developers I know (across several camps) strongly oppose Go, often to the point of ridiculing it.
But then I see Go support being added to everything, usually by a few key people who strongly prefer it. In fact I hear Heroku is internally adopting Go pretty rapidly.
So every time I see an announcement like this, I look up whether Go has added some kind of generics yet. And as usual, they haven't.
But to me, the worst part of this is that the whole community has Stockholm syndrome, being perfectly content to instantly defend every position the Go team makes, no matter what.