(I haven’t checked what the warning says today.)

Well, yeah, that’s why the linked ticket led to a massive improvement:

If you don’t know what git is, you should probably avoid choosing the “confirm” option when you’re warned that an operation is dangerous.

That said, I think the change they ultimately made in the linked issue, which words the warning differently and, more importantly, provides an option to only discard changes to already-tracked files, is a vast improvement.

That depends on what you map “discard” to in your mental model. Whoever designed the VSCode feature chose to associate it with reset+clean, rather than just reset. Presumably that’s why they called the menu option “discard” rather than “reset”. (But I agree that this is a surprising choice, and that they managed to make an already-famously-bad UX even worse.)

Well, yeah, that’s why they updated the warning pop-up. It’s still the case that the user didn’t bother to find out what the warning meant before choosing the inherently destructive option.

Here’s the revised pop-up, according to the linked ticket:

I haven’t checked the current behavior (this whole incident was seven years ago).

I meant it in a completely light-hearted way, but I do wonder if some of the downvoters don’t realize I’m talking about the username.

Understandable; no time to check details when your fuse is that short

The second button is actually a pretty major change!

It means both.

It had a reasonably clear warning, though; a screenshot is included in this response from the devs. But note that the response also links to another issue where some bikeshedding on the warning occurred and the warning was ultimately improved.

In reality, that was added four and a half years after this issue was opened.

Yes, the dialog was changed, as part of this linked issue (and maybe again after that; this whole incident is very old). After reading some of the comments on that issue, I agree with the reasoning with some of the commenters that it would be less surprising for that menu option to behave like git reset --hard and not delete tracked files.

The user clicked an option to “discard” all changes. They then got a very clear pop-up saying that this is destructive and cannot be undone (there’s a screenshot in the thread).

You are saying “yes” to a comment explaining why the Google AI response cannot possibly be correct, so what do you mean “and [it’s] correct”?

Creation is easy, assuming the many-worlds interpretation of quantum mechanics!

Delete prior iterations of the loop in the same timeline? I’m not sure there’s anything in quantum mechanics to permit that…

In the universe where the list is sorted, it doesn’t actually matter how long the destruction takes!

Reminds me of quantum-bogosort: randomize the list; check if it is sorted. If it is, you’re done; otherwise, destroy this universe.

Or Stockholm Syndrome

🤷 That wasn’t my experience, and I used it as my primary dev environment for four years.

It doesn’t go through a translation layer, though. WSL 2 has a whole separate kernel. You can even use GUI apps with Wayland.