Google's "Go"

1. I am of the opinion that a "universal language" is not going to happen, ever. The problem is, different applications require different approaches and capabilities. Even at the assembler level, where the instruction set is pretty limited, there is some diversity. I have my personal preferences, and, when I need to code something, I first consider the task at hand, then decide which language is going to get me to the end point satisfactorily with minimal investment of time. Most of the newer languages out there have specific applications where they really shine when compared to the alternatives, but I have yet to find anything that can do what I want to do as effectively as c. My needs are not universal, nor do I expect my recommendations to be appropriate for everyone. Also, there are rare occasions when it is much quicker to knock something out in one of the various flavors of Basic, or, when the problem is a tough one, delve in to Forth. I personally don't have a need for a new language (I don't even bother with the object-oriented stuff, because it adds a layer of complication to the immediate problem that is not needed).

2. If a new programming language is going to gain adherents, I think it will need to be specialized- target a specific market segment, rather than trying to be all things to everyone. Chances are, if you try to be all things for everyone, you wind up doing nothing very well.

3. Google's goal, I believe, is to make money. They will do anything necessary to achieve that goal.

4. "Go" is most likely a derivative of an in-house solution to a particular issue that Google faced in one of their various ventures, and I suspect they are rolling it out to see if others find their approach to the solution attractive. Since I am not at all interested in programming for web applications, I doubt seriously that "Go" is even worth a brief look for my applications.