←back to thread

310 points speckx | 1 comments | | HN request time: 0.24s | source
Show context
Eric_WVGG ◴[] No.45040621[source]
There’s an important generational component that’s getting missed here.

Most children (American children, at least) grew up on Chromebooks. That instills a certain expectation of how these things work — documents save themselves.

To switch to Microsoft Office means adding a cryptic, unnecessary-seeming extra step. I imagine it feels something like having a laptop that's designed to be shut down before closing.

You’ve all heard the stories about college CS students who have to be told what a folder is — and those are the kids who actually want to work with computers. Now step back to the next generation of lawyers and nurses and novelists and think about their lifetime experience.

Microsoft is just chasing the puck.

replies(8): >>45040637 #>>45040962 #>>45041747 #>>45042131 #>>45042431 #>>45042465 #>>45044996 #>>45047088 #
01HNNWZ0MV43FF ◴[] No.45040637[source]
You can have auto-save and automatic file naming without cloud storage
replies(4): >>45041111 #>>45041145 #>>45044444 #>>45046756 #
1. cosmic_cheese ◴[] No.45041111[source]
Yep. First party and well behaved third party Mac apps have been doing so since… jeez, 10.7 Lion (released in 2011) I think?

The way it works there is that documents are auto-saved to a non-volatile app-specific temp directory until they’re explicitly saved, at which point they’re moved to the specified location and continue to be auto-saved there. Anybody who uses TextEdit as a temp text stash is familiar with this with the hoard of unsaved documents that comes back even after a cold boot.

Microsoft is just motivated to push cloud storage onto usage.