Hacker News Reader

Kinda.

I wouldn't be able to tell you too much about the internals of VSCode.

The 'trouble' with git is, though, that what happens when you run the wrong command can vary from "easy to fix" all the way to "you just lost your work, you shouldn't have run that command".

Which means you need to either be very careful anytime you run git, or you need to learn more about git to avoid the footgun aspects of it.

View on HN

It's kinda sad though because off the top of my head i suspect it's really difficult to actually lose your work. Ie between the fact that the content store stores.. well, all content, until it's GC'd, and the obvious reflog, you can almost always get back your data.

The downside to this though is the type of novice most likely to make a mistake in "losing" their data will also not know how to recover their data.

> it's really difficult to actually lose your work

If it's been checked into a commit, sure.

But if you discard changes which haven't been checked in, then the work is lost.

Reply on news.ycombinator.com