3 ms·
The problem with both the new model and the old model is they combine two concepts: storing your work so it isn't lost by act of God or stupidity and permanentl
by wvenable 14y ago
The problem with both the new model and the old model is they combine two concepts: storing your work so it isn't lost by act of God or stupidity and permanently committing those changes to a specific named file and version.
I want my work continually saved so that I never lose anything but that doesn't necessary mean I want it committed every minute. What I really want to do is commit my current work to a new name leaving the original document unchanged. Duplicating then reverting achieves the same result but feels much more like I'm doing something to please the machine instead of the machine fitting to what is a common work style.
- mgkimsal 14y agoWell put. Again, we're being forced to do the work for the machine. Having multiple automatic commits happening in another area that is something we can pull back in between actual manual 'commits' ('saves') would have been a much better alternative. Once I 'save' to a different file name, from what I understand, automatic saves are still happening to the original file and filename - why? That makes no sense however you slice it.