Meanwhile at Github:
@kofa: Is kofa = kofa73? Then thank you for improving my English!
Sorry, but I don’t agree on this. A crash is never a design option, it’s never intentional. It’s a failure which happens due to a condition that wasn’t accounted for. In other words, it’s a bug.
Explicitly terminating a program, on the other hand, is a precise choice, which normally is dealt with more or less gracefully: as you said earlier, if you decide that the best option is to terminate, you print a message or write a log, so that the reason of the critical error can be reported.
This is a controlled termination, not something that happened because the program didn’t even contemplate that situation.
1 Like
Sorry, was just a typo fix, but may help future searches.
Yes, if there’s a catastrophic failure. But if it’s about failing to open an image that’s in the database, then something like the skull icon + error message would be appropriate (even if it was a user’s unexpected action that led to the problem).
An error message flashed up briefly - too briefly for me to even read it all the way through. That’s why I ignored it. It would be better if it were clearer, a skull would definitely get more attention.
That’s true.
btw.: the photograph you chose to illustrate the issue in the bugreport is very appropriate 
.
Yes, whenever possible there should be an error message, and perhaps even recovery.
But my first reply was in answer to
And that’s just not possible. It should be possible if the cause is invalid user input, but even that is hard.
Dat is dieser kölsche Humor!
(Translated: It’s the typical humor of my hometown. Without it you can’t have this)
1 Like