Goodbye, Ctrl-S 521
An anonymous reader writes "'Save your work!' — This was a rallying cry for an entire generation of workers and students. The frequency and unpredictability of software crashes, power outages, and hardware failures made it imperative to constantly hit that save button. But in 2014? Not so much. My documents are automatically saved (with versioning) every time I make a change. My IDE commits code changes automatically. Many webforms will save drafts of whatever data I'm entering. Heck, even the games I play have an autosave feature. It's an interesting change — the young generation will grow up with an implicit trust that whatever they type into a computer will stay there. Maybe this is my generation's version of: 'In my day, we had to get up and walk across the room to change the channel on the TV!' In any case, it has some subtle but interesting effects on how people write, play, and create. No longer do we have to have constant interruptions to worry about whether our changes are saved — but at the same time, we don't have that pause to take a moment and reflect on what we've written. I'm sure we've all had moments where our hands hover over a save/submit button before changing our minds and hammering the backspace key. Maybe now we'll have to think before we write."
Saved, with conditions . . . (Score:3, Informative)
Re:Never used this keystroke (Score:5, Informative)
Ctrl-S? Ain't nobody got time for that! (Score:4, Informative)
I'm busy F4'ing.
Re:Bah, we already said goodbye to CTRL-S years ag (Score:4, Informative)
Esc-ZZ
Welcome to the 1980's... (Score:5, Informative)
Inspiration! (Score:2, Informative)
Many years ago, I lost some changes in a vi clone named "stevie". The real vi saved your changes automatically by the simple (and at the time necessary) method of using a file to store your edit buffer, but stevie used an in-memory edit buffer. After it losing enough changes from that, I decided to write my own vi clone, "elvis", which also used a file to store the edit buffer. This was very handy in the early days of Minix (predecessor to Linux) which had only a 64K address space per process -- it allowed you to edit text files larger than 64K, oooooh!
Re:Never used this keystroke (Score:4, Informative)
Another thing Apple screwed up was dropping the 17" MBP line. 17" Retina MBP? Yes, please. Even if it's the same resolution as the 15", making the pixels just a hair bigger won't hurt; I like a slightly larger machine that can fit comfortably on my lap, without requiring that I keep my legs smashed together lest it fall between them, and has ample component spacing to allow for decent cooling, thank you very much. I'd love an upgrade, but they don't offer anything I find compelling anymore.
Re:Never used this keystroke (Score:4, Informative)
:x for me.
[John]
Re:Never used this keystroke (Score:5, Informative)