Go is the first language where I can actually access the original socket permission error because it was actually passed up.
Now try to trace them as easily as exceptions. Oh wait, you can't unless you wrap Go errors into some struct from a library that isn't in the std lib therefore everybody has different systems to trace errors /s
i'll take exceptions over this (which go has, panic/defer). error is just a convention, it's not an error system.
Because I felt nothing but frustration at most libs I worked with. I (as others before me) ended up grepping error strings.
I can't think of a single language except C where this has been a problem for me. What are you referring to?
Much bad can be said about checked exceptions, but they certainly helped with that problem...