Why Google's Go Might Be A No-Go
After news of Google's Go language surfaced, I went to my programmer friend for some additional perspective on Google's new experiment. He wasn't impressed -- and actually, neither was I. We had different reasons.
My friend's cynicism stemmed from his own experiences as a programmer, where he has seen languages come and seen them go (pun not intended), and been uniformly unimpressed with the parade that's clomped past his window. He had his own distaste for Clojure ("LISP in a VM", as he put it), F# (OCAML for .NET runtime, nothing more), and so on -- not because they're bad languages, but because the effort put into creating a whole new language doesn't seem to have been justified. He looked at Go and saw very little reason to be interested in it over C# or Scala -- or for that matter, Java or even Perl. Languages are not in short supply.
"I don't have anything against a programming language devised experimentally," was how he put it. "But what's the experiment?"