was there some other reason?

Compiling to an additional OS, today, can be a pain in the ass.

Compiling to an additional OS, a couple decades ago, was a monumental ongoing never ending pain in the ass.

It’s weird to me that there isn’t a full four paragraph rant in the Wikipedia article about J# - just complaining about how everyone’s first “Hello World” was guaranteed to fail to compile due to bugs in the file rename algorithm.

The usability failures in J# are the stuff of legend.

Thanks. I hate being reminded about J#.

I have never of anyone calling C# Java.

Sounds like you missed the fun of it’s first release. We (C# developers) all called it Microsoft Java.

Edit: I remember answering the question "What the hell is C#?!” with: “It’s Microsoft Java”.

It gave folks new to the language all they need to know: It aimed to solve the same problems as Java, and didn’t have Sun’s commitment to Open Source behind it.

Ouch. Relying on case sensitivity is a lousy coding choice, anyway. No one is made better off by having a case change carry meaning.

Edit: Before anyone asks, I like case convention as a courtesy, too. But my code doesn’t rely on it.

I read somewhere that the induced electical field shift near a lightning strike is - while orders of magnitude calmer than the strike itself - still powerful enough to burn, maim and kill.

I think it’s what Wikipedia calls “side splash” in the article on lightning injury?

But why?

Probably because having two separate dependency management solutions can lead to a lot of needless headaches.

And it makes particular sense for Gnome to switch over, since Gnome is focused on user space apps. Flatpaks should generally be more relevant and lower risk, long term, since they don’t require root privileges to install.

without some sort of clear ‘Linux Certified’

I think we will get there. Ironically, we might have ‘Steam Certified’ first, for alternate SteamDeck hardware.

I’m the meantime there’s premium brands like System76 and Framework who are making Linux support part of their brand image.

Needing ndiswrapper was bad, but Ndiswrapper was salvation (okay it was fixed wifi, which is practically the same thing, to me…)

Yeah. I’m confident in this change thanks to my equal discomfort configuring either SELinux or whatever OpenSUSE has. Hooray!

But joking aside, this sounds like a good thing and I appreciate all the folks who do understand that stuff and have worked hard on it.