>They will never shoot themselves in the foot. They will never lose work. They will never, ever need to nuke and reclone their repo. You never need to do these

>They will never shoot themselves in the foot. They will never lose work. They will never, ever need to nuke and reclone their repo. You never need to do these things in git either. People only 'nuke and re-clone their repo' because they google something and get awful StackOverflow answers written by idiots that tell them to do that. It's not how you're meant to do things in git. You're very unlikely to actually lose history in git unless you go out of your way to do so. I mean, you might not actually commit your changes, but I'd hardly call that 'losing work'. What's the alternative, autosaving into your history? No thanks. But once something's committed, it is hard to delete it. The reflog exists.