Hacker News Reader

From the article:

> How is it so easy to “lose” your data in a system that’s supposed to never lose your data?

I think the author is mistaken; git isn't "a system that’s supposed to never lose your data". One of its features is the ability to "lose" data in a controlled way; i.e., to rewrite history. If you want a version control that is supposed to never lose data, use Fossil.

View on HN

This is a figurative use of the word "lose", hence the quotes. The beginner comes in with the impression that it's impossible to lose your data with Git, and then manages to "lose" it anyways. Whether it's really lost, or it's just that the user doesn't know how to get it back, isn't relevant from the novice's point of view.

Even if you rewrite history, the data is not lost. The old commits are still in the reflog and can be recovered.

It’s extremely difficult to lose anything in Git once it’s been committed. You’d have to do something pathological or intentional.

It's also possible (if difficult) to recover files which have been git-added and not commited. The only files git can't recover are the ones that it hasn't registered in the first place.

Reply on news.ycombinator.com