In fairness, it’s an old issue and they did put in the work to address the issue report.

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.

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. They did substantially modify the message to make it much clearer, thankfully.

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.

When I left the project they rehired them and let them design the v2 of the project we just fixed.

Lol. Wow.

And that is why I’ve been unable to work myself out of a job in all my long years as a developer.

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.”

That’s why I think it’s important that we bring Christmas back to its true religious roots: Fertility, hunting, and maybe a cult of the dead.

Well, that and I just kind of want to piss off all of my pearl clutching relatives.

But seriously, thank you for the reminder that this can be a particularly hard season.

I hope your solstice is marked by good times with real friends and chosen family.

Lol. Well good guess.

I’m not a primary source or anything, of course. Your comment just matches something I heard once in office gossip.

Sure but an automated ban and manual review and removal could easily leave them blocked for more hours than not, each day.

Blue sky has an owner and investors, right?

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.

Let’s at least block the government agencies from using it in favor of open platforms and protocols to communicate with its citizens.

Yeah. When public services solely use Xitter or Facebook pisses me off. We can and should make that shit illegal.

Yeah.

It sounds delusional, but by their deluded standards it makes sense.

Everyone should want to work themselves to death do build Jeff Bezos’ empire. It’s just logical… At least to Jeff.

I had the privilege of having lunch with an entomologist once, and yes.

Also, some of them keep advanced databases for looking up cool bugs in case they can’t remember them later.

Suoer-computing is a pain-in-the-ass, so my guess is some combination of SUSE picking up top talent that left other Linux vendors as IBM has been purchasing them, and SUSE just being willing to put in the extra work for the added brand recognition.

Yeah. Thankfully, Windows server cleaned up that stupidity starting around 2006 and finished in around 2018.

Which all sounds fine until we meditate on the history that basically all other server operating systems have had efficient remote administration solutions since before 1995 (reasonable solutions existed before SSH, even).

Windows was over 20 years late to adopt non-grapgical low latency (aka sane) options for remote administration.

I think it’s a big part of the reason Windows doesn’t appear much on this chart.

Heh. I don’t think that number was ever official, but I heard it as well.

Heh. I don’t think that number was ever official, but I heard it as well.

That’s certainly a big part of it. When one needs to buy a metric crap load of CPUs, one tends to shop outside the popular defaults.

Another big reason, historically, is that Supercomputers didn’t typically have any kind of non-command-line way to interact with them, and Windows needed it.

Until PowerShell and Windows 8, there were still substantial configuration options in Windows that were 100% managed by graphical packages. They could be changed by direct file edits and registry editing, but it added a lot of risk. All of the “did I make a mistake” tools were graphical and so unavailable from command line.

So any version of Windows stripped down enough to run on any super-computer cluster was going to be missing a lot of features, until around 2006.

Since Linux and Unix started as command line operating systems, both already had plenty fully featured options for Supercomputing.