Comment by PaulDavisThe1st

3 years ago

Software capable of doing some of the tasks people want done is sufficiently complex that it allows you to issue multiple commands for which immediate action would be contradictory. Telling the application to save state but then also respond to a quit command "immediately" would be one trivial example. Tell an application to quit right after you launched any operation that requires on-disk state to be modified would be the more general case. The software is not bad, it's just got enough power to allow you to make your intent ambiguous.

5 comments

PaulDavisThe1st

Reply
xyzzyz  3 years ago

You can make the app window disappear while keeping the disk saving thread. It is perfectly doable.

  • PaulDavisThe1st  3 years ago

    Sure, but is that actually "quitting" ? Depends on what the user actually expects "quit" to do.

    Also, you're assuming that there is a thread that saves state to disk. There may be (and if the state save is a significant operation, there probably should be). But that's far from always the case.