Didn’t you save your document? What does that mean?
It means I want to keep it. I don’t think that is a broken metaphor at all.
It will not come natural to people who are used to work with physical documents that you need to remember to “save” an edit, or the document reverts back to the state it was when you opened it.
in the real world I do not need to name anything to make scribbles.
No, but you need to have a physical document to scribble on, which, after you have scribbled will remain in the state you left it until you take the active decision to throw it away.
I also do not have a paradigm where there is a fork between versions and create a new document that goes off in one direction while the other document goes in another.
Have you never used a copy machine?
At the end of the other documents time, why can’t I just get rid of it if my what if scenario didn’t work out?
Just throw it in the recycle bin? Another real-life metaphor. Do you often find objects in your physical world disappearing without no action from you?
I also have to choose where to keep something if it is going to auto save
Following the typical cloud implementation, you do not. Just start editing. It will be placed in a default folder under a default name until you rename it / and or move it somewhere else. (These operations are usually provided in more convenient ways than in “save paradigm” software, e.g., the name is shown as a title, just click to change it)
They are taking a document that sometimes can take several minutes to load, and might take many minutes to process. They might be excel sheets, they might by python pandas projects, they might be painting projects or 3d renders.
All of these – except the Python Pandas project (see below) – could still (and probably should) work according to a “you edit the doc itself, no need to save” paradigm. The larger the underlying file, the less sense does it make to forcibly have to work on a copy; either in RAM (if it fits) or if it doesn’t fit, the software has to create an on-disk copy of your huge file behind your back, in case you decide to not save. Leading to all these messy “recovery semantics” that no one likes.
Now, the context of this whole thread is IMO GUI software. When it comes to programming/programmatic tools, e.g. Python Pandas, R, Matlab, etc., that is a different thing. There you have a choice to work in RAM or on disk depending on your needs.
It will be placed in a default folder under a default name until you rename it / and or move it somewhere else.
What a nightmare.
Why don’t we just let things default to not auto save but you can turn it on at anytime.
I personally hate it. Absolutely hate it.
I want to put things where I want them the first time when I am ready. I don’t use cloud services, I have my own network and cloud file shares. I don’t want some program choosing when and where to save something for me, because it is extra work finding all these garbage files I didn’t ask for.
It will not come natural to people who are used to work with physical documents that you need to remember to “save” an edit, or the document reverts back to the state it was when you opened it.
No, but you need to have a physical document to scribble on, which, after you have scribbled will remain in the state you left it until you take the active decision to throw it away.
Have you never used a copy machine?
Just throw it in the recycle bin? Another real-life metaphor. Do you often find objects in your physical world disappearing without no action from you?
Following the typical cloud implementation, you do not. Just start editing. It will be placed in a default folder under a default name until you rename it / and or move it somewhere else. (These operations are usually provided in more convenient ways than in “save paradigm” software, e.g., the name is shown as a title, just click to change it)
All of these – except the Python Pandas project (see below) – could still (and probably should) work according to a “you edit the doc itself, no need to save” paradigm. The larger the underlying file, the less sense does it make to forcibly have to work on a copy; either in RAM (if it fits) or if it doesn’t fit, the software has to create an on-disk copy of your huge file behind your back, in case you decide to not save. Leading to all these messy “recovery semantics” that no one likes.
Now, the context of this whole thread is IMO GUI software. When it comes to programming/programmatic tools, e.g. Python Pandas, R, Matlab, etc., that is a different thing. There you have a choice to work in RAM or on disk depending on your needs.
What a nightmare.
Why don’t we just let things default to not auto save but you can turn it on at anytime.
I personally hate it. Absolutely hate it.
I want to put things where I want them the first time when I am ready. I don’t use cloud services, I have my own network and cloud file shares. I don’t want some program choosing when and where to save something for me, because it is extra work finding all these garbage files I didn’t ask for.