Web app > data is in temp > save commits it to disk
Offline app > data is in temp > save commits it to disk
does “temp” meaning RAM, user directory, remote cloud directory, browser temp files, WordPress backend db and “disk” meaning hard drive or one-drive or Google drive or the permanent remote cloud directory, or production db significantly alter the concept of the function?
Might be controversial, but I think “no.” I don’t think there is a difference between me “saving”, for example, a web page in WordPress as the final version, and me “saving” the offline wire frame design to my hard drive, and me “saving” a PDF of the web page to my downloads folder.
Up arrow to a cloud, or down arrow to a platter (which, ironically, is also out-of-date)
You just described upload and download, not save.
is there a difference between download and save?
You’re viewing information held in temp memory and are committing it to a hard drive or more permanent cloud drive for later retrieval.
Yes there is a difference. If you already have the information on your drive you don’t download every time you make an edit.
I think you’ve misunderstood my point:
Web app > data is in temp > save commits it to disk
Offline app > data is in temp > save commits it to disk
does “temp” meaning RAM, user directory, remote cloud directory, browser temp files, WordPress backend db and “disk” meaning hard drive or one-drive or Google drive or the permanent remote cloud directory, or production db significantly alter the concept of the function?
Might be controversial, but I think “no.” I don’t think there is a difference between me “saving”, for example, a web page in WordPress as the final version, and me “saving” the offline wire frame design to my hard drive, and me “saving” a PDF of the web page to my downloads folder.