Hint: it _is_ error handling (as well). Forces me to be half-human, half-compiler and reinvents the convenience of Java's checked exceptions, but without stack

Hint: it _is_ error handling (as well). Forces me to be half-human, half-compiler and reinvents the convenience of Java's checked exceptions, but without stack traces. It might sound bitter, which I don't intent to be, I just cannot fathom why a significant fraction of users seem to be blind to this, or become blind after a while. Must be some kind of Helsinki syndrome. I use Go for the deployment story, but I think (and I know that I'm not alone in this) that error handling in Go desparately needs a runtime-exception-kind-of awakening.