I quite like Reg Braithwaite’s recent post Show, Don’t Tell. It’s a worthwhile read on that phenomenon we’ve all experienced in which we spend breaths and breaths trying to tell someone something to no avail, only to show them out of frustration and be met with a “oh, yeah, I get it”.
More interesting to me though is the comments on that post regarding the venerable “Save” command.
I am of the opinion that “Save” as a concept, as a modality, is deeply anachronistic and whose demise is being heralded, appropriately enough, by the web. As I type this WordPress is dutifully saving my words across the internet, from Vancouver into a database in Toronto, every couple of minutes. It works so well I often forget it’s working at all. And it’s doing so because there’s no file-based save available to WordPress. Yet the vast majority of desktop apps can’t accomplish this amazingly useful feature at all, despite having measurably more capability than my lowly web browser does.
The closest any desktop app that I use comes is TextMate, which has a preference to allow it to save all unsaved documents when I switch context away from TextMate (from editing code to viewing in a browser, for instance). That’s an amazingly handy feature – don’t use TextMate without it – but alas it’s only about 70% of the way to realizing its full potential.
Reg, in the comments on his post, hints that version control of today should be the save of tomorrow*. I love that idea. I hope he expands on that – I smell a rant…. Let’s get rid of “naming” documents and simply tag them instead. Get rid of the “Save” icon and simply store the deltas of all documents that changed on my machine since n seconds ago – and certainly don’t bother me with the details of it!
Apple’s TimeMachine comes pretty close to accomplishing this but its granularity isn’t quite fine enough. However, imagine TM with a per-file view in which, instead of viewing the history of an entire directory, you just browsed the content history of a single file? Right there, in the Finder. Historical timeline scrubbing of a document’s contents from within the document itself perhaps?
In this day, in the land of terabyte drives, let’s just save it all and never again gasp in fear and wonder “did I save?”
* I realize some people, most notably in the Linux world, have been doing this to varying degrees of limited success for years but using CVS or Svn (home dir in git anyone?) seem like a square peg/round hole solution – again, maybe 70% of what it should be.
chris on May 12th 2008 in /dev/random