nyan

Might be usable as a compose key for typing accented characters and such. It wouldn't need to be held for that.

Because "compared to the US" is a very low bar to clear these days.

Sounds like a simple swap error to me. Probably the nurse who was affixing the bracelets got distracted and got the two mixed up, so each baby ended up with the other's bracelet. North Dakota and only two babies born that day makes me think it was a small hospital where a lot of things were being done by hand, and not a lot of checks were being made.

Legally, yes. I'm pretty sure a pilot is still responsible for their aircraft while the autopilot is engaged, too.

Relatively smart people believe boneheaded things all the time, and have done so throughout history. Extreme case: Kary Mullis, winner of the 1993 Nobel Prize for Chemistry. "In his autobiography, Mullis professed a belief in astrology and wrote about an encounter with a fluorescent, talking raccoon that he suggested might have been an extraterrestrial alien."

Probably better just to run the original Masters Of Orion in dosbox, if that's what you're looking for. GOG will quite happily sell you both MoO 1 and 2 at a reasonable price.

My distro's package manager will quite happily install all of those. From the main distro repo, even. I don't see any reason why I would mess around with flatpaks or other distribution methods.

I can literally count on one hand the pieces of non-game software I use that are installed from outside my distro's package manager (there's three if you include the inkscape plugin to drive my vinyl cutter).

So I repeat, this is either a distro issue or related to how you, personally, prefer to manage your system. It is not a general Linux issue.

Oh goody, we might have a real use for the "Printer on fire" message in the Linux kernel again!

True, Linux did solve this decades ago. And then made it significantly worse in the last decade with multiple package managers (apt-get, AppImage, Flatpak, Snap, brew, random .sh install scripts etc.). Remembering how a Linux application was installed and calling its update command is a chore, and updating will probably pull in some other 500MB+ dependency that’s not shared with other apps because of a minor version change.

If your distro is forcing you to use more than one package manager on a regular basis, you need to switch distros.

If you're choosing to use 3-4 package managers simultaneously, even though you don't really need to, that's on you.

Either way, it isn't Linux's fault.

Seriously? You're invoking argumentum ad popularum (which is a logical fallacy to begin with) in a discussion of linux technical details? That's so illogical I can't even.

systemd is a monolith in practice, despite what its advocates like to claim. You can't run just a part of it under another init without doing extra patch-up work (see elogind). Whereas you can run just one GNU utility on top of, or even alongside, someone else's implementation of that or other utilities (for instance, in parallel with a rust implementation that isn't quite ready for the big time yet).

systemd also won't work on anything except Linux. Older solutions also worked on BSD. That matters to some people.

And the issue was never just Poettering's employers. He had a bad reputation in parts of the Linux community long before systemd—he was also the main force behind pulseaudio, which was shipped long before it was ready for actual use in the real world and remained in a semi-broken state for quite a long time afterwards. And he often comes across as personally obnoxious. Nothing like telling someone "I'm not interested in fixing your issues with my project" (except less politely) to get them to adopt your code.

It's kind of like the OS version of putting Doom on everything and anything.