Re:Twelve Years of Go
by JoeyJoJoJr on Wednesday November 10, 2021 @03:53PM
(#29180609)
I want my program to crash obviously during development so that I know of the existence of bugs, which can be ironed out before getting to production.
That's the theory.
In practice it's impossible to exercise all the inputs your programs may get, and then they crash in production when users do things you don't expect.
Which is better than having a bug silently be in production for years to come due to a silent error.
Which is worse than just handling the error where it occurs.
That’s the point of exceptions. They bubble up! I can manage them at a place where it is appropriate.
Something had happened during the processing of this web request? Catch the exception and convert it to an appropriate status code.
You should only ever let exceptions fall through ”main” when the problem is really not something you can manage to handle.
That's the theory.
In practice often people let the exception eater in main handle it, and it either logs somewhere nobody looks or returns this sort of generic error and exits:
https://www.google.com/search?q=Microsoft+Word+has+encounter...
Re stack traces, they're fine I guess, but I prefer a well-crafted error message to 200 lines of irrelevant file locations/functions.