"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.
This is the list I used 27 years ago(1) when I taught at Stanford. It's a
mix of what the previous guy (Bob Hagmann of Xerox PARC) used, what I
read at Wisconsin, with a sprinkling of Sun's stuff. In looking this
over, it's missing some of the Sun stuff, here are some links, some
good papers here especially those that start with "v" (if the formatting
in any of these looks wonky let me know, I have the troff source for
a bunch of these and had to format it just now to get pdfs, might have
screwed something up):
and to toot my own horn, some stuff I did at Sun (and after)
http://mcvoy.com/lm/papers/SunOS.ufs_clustering.pdf
http://mcvoy.com/lm/papers/SunOS.nvram.pdf (proposal, never built)
http://mcvoy.com/lm/papers/lmbench-usenix.pdf
http://mcvoy.com/lm/papers/splice.pdf (hand waving, somewhat built in Linux)
And the Stanford list:
http://mcvoy.com/lm/papers/stanford.txt
(1) Jesus, I'm old. Feels like yesterday I was teaching there.
"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...
https://talks.golang.org/2012/splash.article