There are 0 excuses for not having months of work in a repo, none. I have no sympathy whatsoever. How the fuck do you spend so many months without backing up your project or stuffing it in a repo?

No sympathy. Dude is a shit developer and he learned an invaluable lesson.

[–] AnAmericanPotato@programming.dev 7 points 1 month ago

My guess is that this is a teenager, and this is probably their first experience with git and version control in general. Just a hunch.

Anyway, it is reasonable to expect a mainstream GUI app from one of the largest companies in the world to be approachable for people who do not know all the inner workings of the command line tools that are used behind the scenes. And it is reasonable to expect any destructive action to have clear and bold warnings. "Changes will be discarded" is not clear. What changes? From the user's perspective, the only changes were regarding version control, so "discarding" that should leave them where they started — with their files intact but not in version control.

Have mercy on the poor noobs. We were all there once.

[–] JackbyDev@programming.dev 2 points 1 month ago (1 children)

If you're going to use a git tool, you need to know how git works.

I guarantee you at least half of git users would get glossy eyes as soon as you mention blobs and trees, yet they all still manage to use it daily successfully.

There are 0 excuses for not having months of work in a repo, none. I have no sympathy whatsoever. How the fuck do you spend so many months without backing up your project or stuffing it in a repo?

I need you to listen to me very carefully: THEY WERE FUCKING SETTING UP A REPO WHEN THIS HAPPENED.

[–] Scary_le_Poo@beehaw.org 0 points 1 month ago

No, by his own admission, he was playing around with the IDE. He wasn't interested in the version control, he was interested in the pretty editor.

I suggest you go read the original issue.