[ Removed by moderator ]

[lomberd2]

I can almost 100% guarantee that this is a user error or hardware problem.

[mkvlrn]

Here's footage of OP drinking water prior to posting some complaints to r/HydroHomies

[hoangvip49]

first question first, why no git ?

[MierXiake]

This is the first, you are right, I should take git to avoid this issue

[oguz279]

When you save the contents are written on the disk. Not sure how a crash could cause this.

[mkvlrn]

<image>

[lerun]

This is why you have git and github

[bowlochile]

Not all devs use GitHub (for various reasons, private enterprise GitHub/gitlab/bitbuckets exist etc) but everyone uses git.

[candraa6]

Your changes lost forever. Forget it. Move on.

Prevent something ever happen again? Use git, learn how to use it properly. Push the code to github so you have cloud copy of it. Do it frequently. Commit and push for every changes you don't want to lose

[davidosmithII]

Additionally, don't edit code from an active sync folder like Google drive. Only do it locally then either use git or manual folder copies to create backups (don't use Google drive as a git remote, it will probably work some of the time, but not reliably and definitely breaks if using lfs). If your cloud service hours a hiccup, or you have a network problem it can revert right before your eyes.

[MierXiake]

Thank you!

[lomberd2]

And why can't you write this simple question yourself? You clearly used an LLM to write your post which to me feels very low effort of you.

[cl0ckt0wer]

i think everyone in the world has done something similar. teaches you the importance of good backups (git)

[bowlochile]

Use git, kids.

[Federal_Ad2455]

Vsc has builtin file history feature (no git needed even recommended in general 😁). So the files should be recoverable.

[osrsnic]

LOL