That was a thing, but it was resolved well before Linux became popular.

IME FreeBSD is realistically almost all drawbacks because development happens on Linux. OpenBSD has its selling point I guess, but my personal experiences with it taught me that if you aren't qualified to fix your own problems with e.g. the kernel, you should avoid it. NetBSD has some meaning as the last available OS for a lot of old hardware, so I guess there's that? In-kernel ZFS is cool but hardly worth the hassle unless what you are building is a pure filer, when the unbundled ZFS works well enough.

Weird that Haiku picked it up, what with actual BeOS having been chock-full of GNU utilities. I know because I did the first released port of GNU file for BeOS.

I did, once, about 30 years ago, lasted about 4 months before they went belly up from incompetent management in those early internet days. Small outfit, 20 employees, and I remember the day I knew it was doomed. The big honcho took us three programmers to lunch, telling us we were the future of the company, not those old-fashioned parasites manning the phones. The whole thing smelled so bad we immediately asked the phone people, and he had taken them to lunch the day before. They were the backbone of the company, not those incompetent bit pushers.

Fun while it lasted. He turned down two offers to buy him out, and was broke a month later.

Oh, that explains why BSD which predates Linux is an also-ran, while Linux is the world's most popular operating system and many major contributors told us in so many words that they chose to contribute to Linux instead of BSD specifically because of the license.

Microsoft creates 1140 security flaws

In your world, Herpes makes you popular and desirable?

You mean being attacked by Israel, a country which is actually doing a genocide, with our money, from a nation which was founded on genocide? You're only a genocide apologist.

Move further south, I guess. The rest of the country is much warmer, more livable, and doesn't freeze solid for three months out of the year. The fact that you have to change your clocks twice a year to cope with it isn't my problem.

Given your user ID # I think you know the reason(s)

If that were what I had said, your comment would be spot-on. However, your comment is wrong, and fits its own definition of being in such a stark world than only two choices are possible: perfect or wrong.

To elucidate: I said I was low in sympathy, not devoid of it.

Please learn to read, then learn to comprehend, and then learn to apply what you have learned to the comment you have typed out before clicking "Preview".

No, in actual fact it isn't.

Nice typo. In fact, malicious intent is worse than gross incompetence.

Of course they will claim they tried.

Naziyahoo says what for decades? Bullshit every time? Get fucked, Zionazi.

wat

You mean the fictional starship which has screens everywhere with a UI whose name is known to nerds everywhere?

Most US population centers are in places east of the point in their time zones where the sun is overhead (or due south) at noon, and being a bit west is better than being a bit (or very, for New England) east. This means that DST is mostly the right UTC offset for the wrong reason: Boston should be on Atlantic Standard Time year-round, but Eastern Daylight Time is a name for the same clock setting that is already used there sometimes, so that's easier to legislate. Of course, the people who live west of their true noon line don't think permanent DST would be good, but the fact that we should have no DST and a different map is too nuanced for the position that there's got to be a single simple answer as to how to fix everything, regardless of the situation.