1305
Save icon (suppo.fi)
submitted 9 months ago by to c/funny@sh.itjust.works
278 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 18 points 9 months ago (2 children)

You just described upload and download, not save.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] -2 points 9 months ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 9 months ago (1 child)

    Yes there is a difference. If you already have the information on your drive you don't download every time you make an edit.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -1 points 9 months ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] -2 points 9 months ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •