> do you want to know when something bad can happen in your program, or don’t you?
Almost everything can fail, and we don't need our noses constantly rubbed in it. Knowing how it failed might be interesting, but you're on your own to check for error subtypes and it's rare to define any.
2/3 of the code is way too much boilerplate for delegating error handling when it can be automated more reliably.
Almost everything can fail, and we don't need our noses constantly rubbed in it. Knowing how it failed might be interesting, but you're on your own to check for error subtypes and it's rare to define any.
2/3 of the code is way too much boilerplate for delegating error handling when it can be automated more reliably.