It appears that the behavior actually included a git clean. Which is insane in my opinion.
Yeah. Building a convenient accessible context free way to run git clean...sure feels like the actions of someone who just wants to watch the world burn.
Yeah. That's discussed in more detail in the code change that resulted from the issue report.
It's a ballsy move by the VSCode team to not only include git clean but to keep it after numerous issue reports.
As others discussed in that thread, git clean has no business being offered in a graphical menu where a git novice may find it.
That said, I do think the expanded warning mesage they added addresses the issue by calling out that whatever git may think, the user is about to lose some files.
Nice. Honestly, pretty well corralled, I would say.
Incidentally, I'm amused that one of the more popular responses includes the classic phrase
"Why can't we all just get along"
Which I tend to notice after having had it explained well to me once by someone with more empathy than my own.
I won't belabor it, but they pointed out to me that being tempted to say "Why can't we all just get along" is usually a sign that we haven't actually listened effectively.
So now when I hear or read "Why can't we all just get along", I see that [X] and hear the buzz from "Family Feud", and hear one of the Family Feud host kindly say "No points. Let's try again."
Ooh, that's a good point. I had a similar experience. Specifically, I didn't really know what I needed when I bought my Prusa, so I didn't get all the features. I was pleased to be able to buy/print and mod in a few of the features I was missing in my initial purchase.
I'll second Prusa. I suspect that no affordable entry level 3d printer is really hassle-free, but my Prusa felt more reliable than my level of experience probably deserved at each stage of my journey.
Publicly funded organizations should be required to use open solutions.
If they want to also replicate what they post somewhere open to BlueSky and Xitter, and Facebook, so be it.
That said, I could see carving out an exception for BlueSky if it provides the full open stack (public unauthenticated HTML, RSS, federation, etc ), and only while it does so.
Lol. That's true. I suspect that Xitter doesn't have the staff or engineering talent left to pivot to enforce any new rules internally. It should be possible to catch them in a constant automated ban without hitting anything worthwhile.
Interesting. I wouldn't know, because I code everything perfectly the first time.
Disclaimer: The above flagrant lie was brought to you by my also using rebase and squash to hide all of my mistakes.