News for hackers. Stuff that matters.
Re:Redesigning the Save Symbol by endlessvoid94 on Friday April 05, 2013 @07:59PM (#5501812)
I think the idea of "save" may even go away. For example, there's no save button on google docs.

Computers should never lose your work, you shouldn't have to instruct it.

Re:Redesigning the Save Symbol by Udo on Friday April 05, 2013 @08:26PM (#5501920)
Yet there is value in being able to decide when a versioning point should be created. This is actually a huge annoyance for me when I'm using Apple's apps that are "always and continually auto-saved". Yes, automatic integrity is nice (when it works), but not being able to make certain decisions about a file's state is pretty limiting.
Re:Redesigning the Save Symbol by endlessvoid94 on Friday April 05, 2013 @08:40PM (#5501986)
That's certainly true, but I'd argue for 99% of the time, automatic saving is what you want.
Re:Redesigning the Save Symbol by chiph on Friday April 05, 2013 @11:29PM (#5502523)
The problem is that there hasn't been a good interface to represent that change history, which will allow me to prune dead ends, and visually identify the version that I want to use to start again from. I can't identify that revision as "the one from 1:52 pm" because I don't know when the auto-save happened. What I do know is that I want the one where I used the phrase 'When Sally Met Harry' in the third paragraph, but not the one where I used it in the fourth paragraph.

Remember - it has to work for non-technical users, so saying "just make it work like Git" won't fly.