most errors you encounters are with i/o and are stupid "can't read, can't write or can't serialize". In a network environment (which is originally what go was

most errors you encounters are with i/o and are stupid "can't read, can't write or can't serialize". In a network environment (which is originally what go was made for) you often need to add tracing information, business-level identifiers or processing information related to your state etc. I'm currently writing a fairly complex api in go, and to be honest this really hasn't bothered me once. Not to say it doesn't exists, but with time i've come very suspicious of people complaints over go. Most of the time those complaints come from people that didn't realize they missed an opportunity to have written a much much more elegant solution to their problem.