I clicked delete and then clicked confirm when it asked me if I'm sure I want to delete, and all my files disappeared! What the fuck?!? Fuck this fucking operating system!!!!1!!1one!!!

[–] JackbyDev@programming.dev 3 points 3 days ago (1 children)

Did you even read the thread?

CANNOT EVEN FIND THEM IN THE RECYCLE BIN!!!!

[–] Anticorp@lemmy.world 0 points 3 days ago (1 children)

Yes, that's what it means when it says "files will be permanently deleted, this is not reversible."

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

https://github.com/microsoft/vscode/issues/32405#issuecomment-322155856

Also, check the linked issue to see the bug and UX problems. Particularly the first comment and this one: https://github.com/microsoft/vscode/issues/32459#issuecomment-322160461

I have a difficult time believing this was their fault. It is (was) bad UX.

[–] Anticorp@lemmy.world 0 points 3 days ago (1 children)

Have you actually used VS Code, or are you just doing a bunch of research to disagree with a stranger on the internet?

[–] JackbyDev@programming.dev 4 points 3 days ago (1 children)

I'm not doing "a bunch of research", I just read the thread and the linked issue and I'm annoyed by people's condescending comments about something it seems like they didn't actually read. We shouldn't shit on people for things we believe they did wrong, especially when, if you read the linked issue, it wasn't their fault.

I use VS Codium (basically Code), but I don't use it's git integration other than maybe the occasional merge conflict resolution.

[–] Anticorp@lemmy.world 0 points 3 days ago* (last edited 3 days ago) (1 children)

If the user didn't read that, that's on them. They used a feature they didn't understand, which is part of a version control system that they also didn't understand, and didn't bother reading anything. If you still think they bear no responsibility for their actions then we'll just have to agree to disagree.

Since they don't actually have a git project tied to their files, "all changes" means "files created". If they did have git configured then it would mean "changes since the last commit", and it wouldn't delete the files.

Edit: I will concede that it's probably not immediately apparent to someone not familiar with the system that uncommitted files will be deleted if you use the revert button. But that comes back to understanding things before you go around clicking buttons that say the action is irreversible. At a minimum, they bear responsibility for not knowing what they were doing, and still charging ahead full steam.

[–] JackbyDev@programming.dev 1 points 3 days ago* (last edited 3 days ago)

I don't think it's reasonable to assume most people would think something that says "discard all changes" would run git clean -f instead of something like git reset or git reset --hard.

The message is better now, regardless. Running this in Codium I get "Are you sure you want to DELETE 2 files? This is IRREVERSIBLE! These files will be FOREVER LOST if you proceed." Which is way more clear than something like "discard ALL changes" without even giving you any sort of summary about what those changes are. Especially given the logic from the linked comment on the second issue,

Oh what is this? Yes, let's initialize, git sounds awesome, people use it.

Oh what is this? All my files appear in this list... but they didn't before. It looks like its touching my files, I don't like that, how to I get them out of here?

Oh what is this? Discard all changes sounds a lot like what I want to do. 💀

Given the "change" they just did was to click "Initialize Repository".