It really depends on what the app is though, yeah? If I'm in document processing or spreadsheet where you might be working for long periods where a 5min auto-save kicks in could be convenient. However, when I'm writing code that then needs to make rapid changes like updating CSS/JS/etc to be refreshed in browser, then I'm not waiting 5 mins for an autosave. Cmd-S, Cmd-tab, Shift-Cmd-R, boom.
However, Cmd-S is so engrained into the muscle memory, that it's almost instinctual to hit it after every press of a semi-colon.
If I type in rm -rf / and pause for a moment trying to remember if I’m trying to delete /var/log/apache2/ or /usr/local/var/log/apache2/ in a dev environment that auto-executes code when I save it I would strongly prefer that it wait until I manually save.
Which is why I like Autosaves that save a copy. Blender for example autosaves project files into it's own location (and keeps that location clean). If you have a crash you can still go for that autosave file and it works in most cases – but it isn't saved in the folder you are working in.
For certain programs this would be overkill of course, but for others it would be quite cool.
It’s interesting. I use vim which has auto-recovery built in. But I also compulsively save. vim is so much faster than most conventional IDEs that it’s just not worth it for me to look for an alternative to that pattern.
> However, when I'm writing code that then needs to make rapid changes like updating CSS/JS/etc to be refreshed in browser, then I'm not waiting 5 mins for an autosave. Cmd-S, Cmd-tab, Shift-Cmd-R, boom.
VSCode has an autosave that's triggered when you change a file.
I would guess that they swiped that idea (among many of the core features of VSCode) from IntelliJ a good 10 years after they implemented it. Too bad they can't steal more sane ideas from JetBrains' IDEs, I might actually consider switching ;)
However, Cmd-S is so engrained into the muscle memory, that it's almost instinctual to hit it after every press of a semi-colon.