Why do we say save the file/image instead of keep/preserve the file/image? Is it because the original meaning was to save (rescue) the object from being lost?
migrated from stackoverflow.com Oct 24 '11 at 16:03
|
As always with etymologies of computer related terms I have turned to the jargon file. Now, though it does not have a mention of the term specifically, it does describe following (you can read only the highlighted part):
So, possibly the term save was chosen because it was possibly already used for the punch cards to separate the ones that need to be stored, kept, preserved... |
|||||||||||
|
|
Saving is different from preserving or keeping in computer science; data that has not been saved has not been written to persistent memory. In reality this is a writing operation but "save" has been used to express the meaning to a less technical crowd. Save means to write the file to your computer in a way that will persist; "keeping" the data where it is before the save operation is actually not saving or writing the data. You are not keeping or preserving because the data exists only in volatile memory, you can keep or preserve it in volatile memory but it is not written to a permanent location. You could think of the data as being saved from being lost when the volatile memory is lost, which happens each time the computer shuts down . The Free Dictionary has a helpful Computer Science related definition of Save:
|
|||||
|
|
The OED’s first citation for the use of save in this sense is from 1961. There are several earlier uses of the verb which could have influenced the choice. They include:
|
|||||||
|
|
As some of the others have pointed out, "save" does indeed mean to store it to persistent disk memory. However, that still doesn't explain why someone chose the word "save" for that activity, as opposed to "keep", "store", "preserve" or "persist". While I cannot find any evidence as to the actual origin, I would put out the possibility that "save" was selected simply because it sounded cooler :) It may sound flippant, but I'm being entirely serious. Engineers in my experience are fond of making word choices for purely aesthetic reasons, and "save" was coined long before the days when User Experience design and natural domain language came into vogue. Also consider some of the variant forms, like "autosave" and "unsaved". Autokeep? Unpreserved? They would work just as well grammatically, but they don't exactly roll off the tongue. |
|||
|
|
