Though initially the diligent programmer will check each and every call with if err != nil {}, there comes a time when laziness kicks in. When that time comes, you'll get hit with unexpected behavior (aka: tracking down nil references).
You might argue the same would happen with exceptions. Yes, they will blow up in your face as well if you fail to catch them. But when they do, you'll hopefully have a well specified restriction that enables to you pinpoint the issue almost immediately.
Basically, with exceptions you know the guy who shot you in the gut because you were being lazy, whereas with Go's error system he's hiding behind the bushes with a dozen or so of his conspirators.