this post was submitted on 20 Nov 2024
873 points (97.6% liked)
Programmer Humor
19804 readers
47 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Have you actually used VS Code, or are you just doing a bunch of research to disagree with a stranger on the internet?
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.
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.
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 likegit reset
orgit 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,
Given the "change" they just did was to click "Initialize Repository".