Yesterday morning I came across a link to Eric S. Raymond's blog to The big break in computer languages whereupon he hammers on C++ (deservedly so as it is completely out of reach to a hobbyist like myself, i.e. the learning curve is much too steep) and also links to a previous blog, The long goodbye to C. I had heard of Go, of course, but so far wasn't aware of any major projects coded in it. I checked out the Website and started on the tutorial which failed because I needed to have the GOPATH environment variable set, which is trivial. Then I tried again and was met with: Code: $ go get golang.org/x/tour/gotour package golang.org/x/tour/gotour imports golang.org/x/tools/godoc/static imports golang.org/x/tools/imports imports context: unrecognized import path "context" Hmmm, a quick Google shows that the context error basically means that my run time Go is too old: Code: $ go version go version go1.4.2 gccgo (GCC) 5.5.0 linux/amd64 . on Slackware 14.2. Okay, I understand things get out of date, but shouldn't such a highly touted compiler at least print as an error message something useful like, "Your copy of Go is too old..." That seems a bit more acceptable than what was printed. It's quite likely that "context" is much newer than my version can support, but that didn't seem immediately obvious. What good is it going to be to put Go into a stable Linux distribution if it's far enough out of date as to be useless in a matter of months? I have a project that should be converted from C/GTK2 to something else (I thought about Python3 with PyQt, but that combination is wildly inconsistent across distributions the last time I checked. Python3 with Tkinter is about the only sane choice). After reading ESR's almost breathless endorsement, I thought Go might be a useful choice. Now I am not so sure. Those of you that know Go, convince me that I'm being rash by dismissing it after a few minutes.