| ▲ | svantana 9 hours ago | |
> At some level, the simplest thing to do is to give up and crash if things are no longer sane. The problem with this attitude (that many of my co-workers espouse) is that it can have serious consequences for both the user and your business. - The user may have unsaved data - Your software may gain a reputation of being crash-prone If a valid alternative is to halt normal operations and present an alert box to the user saying "internal error 573 occurred. please restart the app", then that is much preferred IMO. | ||
| ▲ | lmm 3 hours ago | parent | next [-] | |
Crashing is bad, but silently continuing in a corrupt state is much worse. Better to lose the last few hours of the user's work than corrupt their save permanently, for example. | ||
| ▲ | Krssst 8 hours ago | parent | prev | next [-] | |
> Your software may gain a reputation of being crash-prone Hopefully crashing on unexpected state rather than silently running on invalid state leads to more bugs being found and fixed during development and testing and less crash-prone software. | ||
| ▲ | Calavar 8 hours ago | parent | prev [-] | |
> If a valid alternative is to halt normal operations and present an alert box to the user saying "internal error 573 occurred. please restart the app", then that is much preferred IMO. You can do this in your panic or terminate handler. It's functionally the same error handling strategy, just with a different veneer painted over the top. | ||