this post was submitted on 20 Nov 2024
851 points (97.4% liked)

Programmer Humor

19623 readers
1 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

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
851
Microsoft Please Fix (lemmy.zip)
submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]
330 comments fedilink hide all child comments
 

The real report

Bonus

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] -1 points 1 week ago* (last edited 1 week ago) (1 children)

This is 2000% user error lmao even tho VS Code is a pain in the ass on w*ndows

EDIT nvm my reading is 2000% user error

[–] [email protected] 3 points 1 week ago (1 children)

Did you actually read the thread and see the bug they found where it deleted files unassociated with git?

[–] [email protected] 2 points 1 week ago (1 children)

I did but I must have misread maybe? Because what it looked like was it picked up the existing fucked up git repo but if vscode did the fucking up the less of a skill issue 😮‍💨😮‍💨😮‍💨

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago)

It was on this linked issue. They discuss the UX of it more there and I think it's a little better. https://github.com/microsoft/vscode/issues/32459

In particular, this comment helps explain why I think this is (was) a problem.

As we discuss this, keep in mind that most users who hit the "omg where are all my files" issue come into following these three simple steps:

  1. Oh what is this? Yes, let's initialize, git sounds awesome, people use it.
  2. 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?
  3. Oh what is this? Discard all changes sounds a lot like what I want to do. 💀

People don't hit this issue because we have that action; they hit it because they want to clear that list. And they will go through great lengths to get there, even if not knowing what their doing or after warned that they are in dangerous waters.

Coupled with the behavior of this "discard all" being git clean rather than git reset, I get the complaints.