Why do people focus so much on that random side comment from Pike during one talk he gave a long time ago? It's hardly the language philosophy and it's really hard to believe that Pike actually thinks Google programmers are bad or even average given that he has seen the hiring process.
> In short, Go is not just a programming language. Of course it is a programming language, that's its definition, but its purpose was to help provide a better way to develop high-quality software, at least compared to our environment 14 plus years ago.
> And that's still what it's about today. Go is a project to make building production software easier and more productive.
I think there is an idea that Go is "software engineering for the masses", and that's why the word "easier" is used, and not "simpler". "easier" is fine when you're starting out and you don't know what you don't know. As times goes on, you start understanding more because you have more experience, and so you may yearn for something simpler, with less abstractions, more control. Go isn't the best language for this, but it's also far from the worst.
> The key point here is our programmers are Googlers, they’re not researchers.
I take that to mean that they're searchers, not researchers. I.e., "Googlers" here means they use Google to search for answers, not that they're Google employees.
In this context, Googlers does in fact mean Google employees. The context from the surrounding talk[1] talks about Google's use cases such as concurrency being a key part of the language, etc.
Inside of Google the term 'Googler' unambiguously refers to co-workers; not to people who just happen to use Google products. (Source: I used to work there.)
