3 ms·
> Go’s error handling is not noise, it’s signal. It's a ridiculously noisy signal, which makes it difficult to distinguish from noise: because all the error ha
by masklinn 3y ago
> Go’s error handling is not noise, it’s signal.
It's a ridiculously noisy signal, which makes it difficult to distinguish from noise: because all the error handling looks the same and is extremely verbose, it's difficult to distinguish special cases you need to pay attention to.
Tons of languages have "errors as values", Go stands out in its verbosity, as well as its lack of safety / certainty.
- thiht 3y agoOf course Results/Options would have been better from the start, but it’s too late for that. As a dev though I infinitely prefer Go’s error handling than exceptions for instance, specifically because of the verbosity and explicitness