this post was submitted on 13 Nov 2025
1288 points (98.6% liked)
Funny
12307 readers
913 users here now
General rules:
- Be kind.
- All posts must make an attempt to be funny.
- Obey the general sh.itjust.works instance rules.
- No politics or political figures. There are plenty of other politics communities to choose from.
- Don't post anything grotesque or potentially illegal. Examples include pornography, gore, animal cruelty, inappropriate jokes involving kids, etc.
Exceptions may be made at the discretion of the mods.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
No, download would be a down arrow from a cloud. "Saving" on a modern system typically implies a local cache paired with a cloud backend.
Not my fault that they're wrong.