> Something is already really wrong with your app if it tries to do things like this. The base philosophy of "if it's wrong it should fail" is primarily for de

> Something is already really wrong with your app if it tries to do things like this. The base philosophy of "if it's wrong it should fail" is primarily for developpers, and shouldn't apply to generic customer products. If it's dangerous, or will cost money, or will have severe ill adverse effects, I'd see the point. If a credit card transaction is wrong, make it fail. But short of these extremes, the default should be graceful handling of exceptions and help the customer app keep going and deliver some value to the user even if it's poorly written, mishandling the context.