Nice article: http://jimplush.com/talk/2015/12/19/moving-a-team-from-scala-to-golang/

Team size scaling seems to be the problem there. I think Clojure would not have done better there?

As it is relatively hard to find many Clojure developers

I dunno, I'm all like

> 2015
> using Go

I read the same article today and I found it very inspiring. I always wondered why someone like Rob Pike would create a language with such a feature set. It made no sense, someone with such an experience, creating a new language. But after reading that article, it was kind of obvious. He made that one for google, one of the businesses in the world with probably one of the largest developer counts. So he needed something that limits in every way, but makes building across multiple teams a breeze. So, this is how go lang came out. And it makes sense for large firms. Especially as the number of developer rises that does not have a scientific background, especially not in language theory. Why waste the time learning Applicative Functors if you could implement 100 features in that time. I think this is a step further into the assembly line work direction that business wants to move developers to.

Maybe I'm just weird, but I can't understand how, say, allowing null pointers being anything but a wrong decision.

But other than that I can see the appeal of deliberately simplifying the language to the designer and to businesses - I guess that's one of core things that led to the success of Java.

And the niche go targets - a plumbing language for web infrastructure - doesn't make it's simplifications too painful, probably.