The "functions returning errors" design still hasn't settled well with me. I was pleased as punch when I first saw "Try-Catch-Throw" pitched by Borland at Comde

The "functions returning errors" design still hasn't settled well with me. I was pleased as punch when I first saw "Try-Catch-Throw" pitched by Borland at Comdex circa '92 and I grasped what that meant for how I write programs. Go's design seems like a step back for my sensibilities. I do like how it forces you to do something when the error is easy to contain, but checked and unchecked exception handling seems to make it more obvious how to treat an exception. Of course exception hierarchy can be abused, but done properly it seems more descriptive and flexible. Only when people abuse exceptions to drive business logic have I found them unappealing. I'm adapting though.