I wholeheartedly agree with this article. I've had great success with Go's reliability. Another important point to make is that when programs written in Go do

I wholeheartedly agree with this article. I've had great success with Go's reliability. Another important point to make is that when programs written in Go do fail, it tends to be trivial to figure out why. There's no type hierarchy like most OOP languages and no method_missing magic like Ruby. I can typically just trace the logic backwards from the error to the cause. Most bug reports I receive for my open source Go projects get fixed in minutes.