autosave [LWN.net]

autosave

Posted Jun 11, 2022 0:04 UTC (Sat) by marcH (subscriber, #57642)
In reply to: autosave by giraffedata
Parent article: Per-file OOM badness

Maybe not "niche" but for sure it is not the most common activity in a text document. When undo is not enough, simply use version control or its grand daddy: make a copy. Done.

Like it or not the "save" button is disappearing really fast and very few people struggle to switch to the new, more powerful and more flexible ways.

to post comments

autosave

Posted Jun 11, 2022 12:18 UTC (Sat) by rschroev (subscriber, #4164) [Link] (3 responses)

> Like it or not the "save" button is disappearing really fast and very few people struggle to switch to the new, more powerful and more flexible ways.

The way I see it, the new ways are more convenient for most use cases and may well be the way forward, but the old way with the save button is the one that is more powerful and more flexible (but requires the user to have a bit more discipline).

autosave

Posted Jun 11, 2022 13:30 UTC (Sat) by Wol (subscriber, #4433) [Link]

> the new ways are more convenient for *MOST* use cases

Emphasis added ...

Cheers,
Wol

autosave

Posted Jun 13, 2022 12:43 UTC (Mon) by mathstuf (subscriber, #69389) [Link] (1 responses)

Of course, there's the issue that showed up on a machine I was helping out with where MS Office lost the ability to "Save As" (the directory selection never showed up). This was…OK, but when it lost even "Save", the only way to save work was:

- autosave to OneDrive (could not choose a local directory AFAICT) behind a Microsoft account
- "Send" the document over email then save the attachment from the draft message
- reinstall MS Office (which forced an upgrade)

There are all kinds of complexities involved in this new mechanism and I'm sure all kinds of new bugs will show up because of it too. I love how companies seem to be ensuring future prospects by deleting working code in preference for new, buggy code.

autosave

Posted Jun 13, 2022 13:30 UTC (Mon) by Wol (subscriber, #4433) [Link]

> I love how companies seem to be ensuring future prospects by deleting working code in preference for new, buggy code.

The problem, of course, is when your working code stops working because of a forced upgrade somewhere else.

I'm now an Excel VBA programmer in practice - oh how I wish I could push all that crap into a decent database ...

(And no, I don't fancy the politics that would entail ...)

Cheers,
Wol