On Go
This is one of a series of posts on languages, you can read more about that here.
A grab bag of observations on the Go programming language, positive and negative. It bucks some orthodoxy on what a good effective language is supposed to look like. It makes sensible engineering decisions and is squarely in the category of languages I consider viable for server-side systems that you have to live with over time.
On Languages
I have been playing around with Erlang, Scala and Go more and more, to the point where I'm able to draw conclusions about them as production languages. I don't consider myself expert in any of them, but like most people in my line of work I have to be able to make judgments in advance of deep understanding. I've also spent time to a lesser extent with Rust, not enough to decide anything much. I've been foostering with Erlang and Scala on and off for years, Go and Rust are more recent.
Ubuntu Lucid 10.04 on Thinkpad W500
After over 3 years at 10 hours a day it was time to retire the thinkpad T60.