Comment by hellcow

>if err != nil { gets old even faster.

I don't understand this complaint about Go. Either a function can result in an error or it can't. If it can result in an error and you don't handle that error, your program's behavior is undefined. Undefined behavior is a bad thing.™

Go forces you to handle the error (or explicitly ignore it). That design choice results in remarkably stable programs.