3 ms·
Your definition of safe is not mine. I have no doubt the data is preserved - 'unrecoverable state' is too strong. Its not safe in the sense that if i make a ch
by jheriko 13y ago
Your definition of safe is not mine. I have no doubt the data is preserved - 'unrecoverable state' is too strong.
Its not safe in the sense that if i make a change on submission day and need to revert it then its more complicated than it needs to be. Granted I should not be using something I don't have sufficient mastery of in that kind of scenario, but its not always so simple.
My data being 'safe' is worthless if there is a steep learning curve to recovering it.
- nbouscal 13y agoThe learning curve is not that steep. Compare it to learning vim or emacs, for example, and it's no contest. The learning curve is basically: 1) read Pro Git, 2) play with git for a little while. That's about it. If you can't afford that learning curve for something that is a core part of your workflow, you're doing something wrong.