4 ms·
> Apparently, nothing was catching that exception, so the whole process was terminated. Apposite moment perhaps to refer to the mind-boggling finding in "Simpl
by cannam 6y ago
> Apparently, nothing was catching that exception, so the whole process was terminated.
Apposite moment perhaps to refer to the mind-boggling finding in "Simple Testing Can Prevent Most Critical Failures: An Analysis of Production Failures in Distributed Data-Intensive Systems" (Yuan et al, Usenix 2014 https://www.usenix.org/conference/osdi14/technical-sessions/presentation/yuan https://www.usenix.org/conference/osdi14/technical-sessions/...):
"almost all (92%) of the catastrophic system failures [in the real-world study] are the result of incorrect handling of non-fatal errors explicitly signaled in software"
- NikolaeVarius 6y agoI lends this leads credence to the go way. Verbose because than its hard to mess up
- Groxx 6y agoI mean... not really. This is the equivalent of `if err != nil { return nil, err }` which is so common it's a mindless default behavior worthy of memes: https://pbs.twimg.com/media/DCIF7-2W0AEAv9c.jpg https://pbs.twimg.com/media/DCIF7-2W0AEAv9c.jpg It absolutely results in the same kinds of failures.
- diamondo25 6y agoSaw one case where it was `if err != nil { return nil }`, so the error was completely ignored and function exited without error...