In the words of Rob Pike:
"The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt. – Rob Pike 1"
"It must be familiar, roughly C-like. Programmers working at Google are early in their careers and are most familiar with procedural languages, particularly from the C family. The need to get programmers productive quickly in a new language means that the language cannot be too radical. – Rob Pike 2"
So a language that makes it quite easy for enterprises to deal with developers as cogs.
Source:
http://channel9.msdn.com/Events/Lang-NEXT/Lang-NEXT-2014/Fro...
I don't see what that has to do with offshoring. Developers of the kind Rob Pike is referring to exist everywhere in the world.
I do enterprise consulting, in projects which happen to always have some kind of offshoring involved.
Projects where the languages are easy to pick up and anyone can do it, are always the first on the pipeline to give away.
Are you really saying that Rob Pike is part of some kind of conspiracy to offshore all the coding that's currently being done at Google SF? Golang has been around for a while now, and there's no sign of that happening.
No, I am just stating that the goals of having the language designed for such target audience, can have that as side effect.
Just like it happened with Java.
It's pretty bad that people outside the SV can code /s
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.
Exactly. :)
Software is more than just language features. Rob undoubtedly meant that he wanted it to be quick to be understood by a vast majority of Googlers, so that they can focus on writing good software.
Yet Google is known for having one of the hardest hiring processes, where they even give the candidates CS subjects to study before the interview.
He really said they're not capable?