Personally, I think in a perfect world there would be a more widespread distinction between "save" (something that happens automatically whenever changes are made, to "save" the data from some unexpected calamity like power failure) and "commit" (what you're talking about, which most people think of as "saving"). I doubt it would realistically catch on any time soon outside of tech circles, though, due to the confusion it could cause the average user - "New, open, print, commit, exit... now where the hell is the damn save button?!"
Actually, it's the concept of 'save' that is unintuitive. The EPOC systems just kept your data, and it's one of the nice features that sublime gives you. In an ideal world, a document would keep its entire change history as a graph (not just a single line), and you wouldn't 'save' a copy, you'd name a particular revision of it so that it was easy to get back to later.
