Slashdot Mirror
Goodbye, Ctrl-S
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."
Your material will be saved to the cloud where the NSA computers can check it and make sure you're not doing anything illegal. But please just ignore the prying eyes, citizen, and get back to work for the Man. After all, he owns the NSA now.
Quite possibly, he's a Mac user, so it would be Command-S. That, or someone loves their mouse a little too much and never bothered to learn keyboard shortcuts.
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
I'm busy F4'ing.
Trolling is a art,
Esc-ZZ
... when GNU Emacs had auto-saving and backup versioning at any keystroke granularity you liked thirty years ago. Next we celebrate the boon of split screen editing.
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!
Late 2011 17" MBP here... Apple screwed the pooch removing the Save function from their apps; though their current online documentation implies that it's back (and, indeed, it is in TextEdit, the only Apple app I use).
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.
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
:x for me.
[John]
Shit better not happen!
I want Save As back as a first-class citizen as much as anyone, but the entirety of your rant there is simply flat-out wrong. You say there's no save option, but (as you half-acknowledge after complaining it doesn't exist) there is - and yes, it shows up in every document-based app. You say you have to go to Finder to duplicate a file, but the whole complaint here is that Save As has been replaced by Duplicate in the menu. The actual, still 3-step process is: Choose "Duplicate" (no need to save beforehand as it is the current state that is duplicated), type new file name, and (either the first time you do an explicit save or when you close the new document) deal with the Save dialog. The only way that is more difficult than Save As is that it disconnects renaming the new file from the save dialog. And if you prefer documents revert to the last manual-save state on close, simply check that box in the system preferences.