Per-file OOM badness [LWN.net]

Per-file OOM badness

Posted Jun 5, 2022 23:16 UTC (Sun) by neilbrown (subscriber, #359)
In reply to: Per-file OOM badness by marcH
Parent article: Per-file OOM badness

What ..... do you mean that "autosave" actually saved the document just like clicking the "save" button would?
That is totally broken.
Deliberate-save and auto-save are both important, but they are different.

This relates to the comment by NYKevin above:

> if an autosave happens right before the player loses, the game may become soft-locked

That is nonsense. After a crash/power-off you should always be able to choose between what you deliberately saved (if that is ever an option, which sometimes it might not be) and what was autosaved (which must always have happened "recently").

Any other behaviour is a bug.

to post comments

Per-file OOM badness

Posted Jun 6, 2022 1:47 UTC (Mon) by NYKevin (subscriber, #129325) [Link] (1 responses)

As far as video games are concerned: I was specifically discussing a hypothetical in which manual saves don't exist, and the game "always" saves all progress. In this context, there is simply no such thing as "what you deliberately saved."

Per-file OOM badness

Posted Jun 6, 2022 1:49 UTC (Mon) by NYKevin (subscriber, #129325) [Link]

(To be clear, this is a real type of saving that has actually been implemented for some games, most notably Minecraft. Minecraft gets around it because the player respawns after death, unless permadeath is enabled for that world, and so soft-locking is nearly impossible in practice. But there are many games where a respawning player would not fit the narrative or tone of the game.)