Comment by foldr
8 years ago
Your responses to K0nserv and singhrac suggested that you were defending the claim that golang was "designed for" outsourcing.
If you're making the weaker claim that Go's design "can" have the effect of triggering outsourcing, then that's speculative and consequently rather difficult to refute. But you haven't provided a single piece of evidence that this has actually occurred, so far as I can see.
I was making the claim that can be a side effect of its design and the way the community is against common features in modern languages, deemed too complex.
Lets see how it looks a few years from now, given that it is becoming a mainstream language thanks to Docker and K8s adoption.
Many of those features (e.g. generics) are in Java and/or C#, which are nonetheless widely outsourced.
True, however Go is like a Java or C# 1.0, they did not start as they look today.
So Go is in the right track to follow their path.