Right, sorry for the patronizing tone, I’m sure you know all this. But I tend to lament the overall tendency for people to write cleanup code in general for th

Right, sorry for the patronizing tone, I’m sure you know all this. But I tend to lament the overall tendency for people to write cleanup code in general for this kind of thing. It’s one of those “lies programmers believe about X” kinds of scenarios. Your program will crash, and you will hit situations where your cleanup code will not run. You could get OOM killed. The user can force quit you. Hell, the power could go out! (Or the battery could go dead, etc.) Nobody should ever write code that is only correct if they are given the opportunity to perfectly clean up after any failure that happens. I see this all the time: CLI apps that trap Ctrl-C and tell you you can’t quit (yes I bloody well can, kill -9 is a thing), apps which don’t bother double checking that the files they left behind on a previous invocation are actually still used (stale pid files!!!), coworkers writing gobs of cleanup code that could have been avoided by simply doing nothing, etc etc.