You might like "save continously but call it 'history', offer a save button but that just names the current revision"

This lets you throw away and start over, but also gives you infinite undo even after "loading" an older version.

We could have both. The "save" button just becomes a pointer to a specific point in the revision history, the same way we already have that with git.

I've had my code editor's configuration set to auto save for at least 15 years at this point. I've never had the problem of not being able to throw something away that I wanted to throw away - either it's in the git history (broad edits), or it's in the undo-history (fine edits). It helps to have an undo history that survives restarts and that preserves branches, which I guess may not be a default for every editor