> Without that (which would be similar to not checking the err in go) it explodes or throws to a layer up that may not expect it. It's not similar to that at a

> Without that (which would be similar to not checking the err in go) it explodes or throws to a layer up that may not expect it. It's not similar to that at all. Without it, the exception bubbles up until it gets caught somewhere, or crashes the program with a useful stacktrace. With golang, it just goes undetected, and the code keeps running with corrupt state, without anyone knowing any better.