To the contrary: they have demonstrated they're not teenagers. Kids don't use old memes as those are "uncool", and underpants gnomes are something that came out 28 years ago.

I see you haven't seen any version of GNOME from the last 18 years.

For Microsoft, that would be the wrong way. Instead of making many Microsofts, the govts should go the other way, and make zero!

That's why not running uMatrix or disabling its deny-by-default mode is insane.

Yes, but Red Hat, even under IBM's rule, isn't anywhere as evil as Poettering wants. I'm not good at who-works-where-ology, and haven't been paying any attention at all in the last few years -- but I am not aware of even a single Red Hat engineer who would deserve disrespect. Lennart is where he belongs.

If Google wasn't evil, we'd have working JXL in 2021. The lack of pressure also allowed Mozilla to waste years writing a NIH implementation in their own toy language. The benefits from JXL are pretty great all around, including both lossy and lossless, it's a pity we didn't get it sooner.

Google pushed their own WEBP and AVIF hard despite neither being as good as the rest. WEBP is very slow and hardly better than old JPEG, AVIF is at least usable but loses to other modern formats for anything except extremely low bitrates.

Shooting a driver who was attempting (partially successfully) to run over his teammate is not "treading on others", it's doing his duty. Even though the orders he received were issued by a deranged orange monkey, assaulting an officer with a deadly weapon (such as a car) is still supposed to be responded to with deadly force.

Add half an hour of driving and parking, 10+ mins of getting herded through the crowds at the entrance, with delays designed to make you buy overpriced popcorn, 30 mins of adverts for new movies, half an hour again of driving back.

All of that at a fixed time of the day, while at home you can watch a movie (from the disk or via streaming, not broadcast TV) at a time of your choosing, including pauses.

To elaborate: the C standard never mandated any particular character set except for a basic "portable subset" smaller than ASCII; implementations could freely add more or less, possibly necessitating trigraphs. Later revisions disambiguated what character classes can be used in identifiers and string constants, but in principle you were allowed any symbol supported by your platform since day one.

That's the standard; implementations differed. In particular, GCC was hesitant to allow non-ASCII (in a bid to save our sanity) but caved several years ago wrt allowing Unicode identifiers by default.

Python gets even worse: it uses WHITESPACE for syntax!

Except it works in pretty much anything, including C. Slashdot is one of last holdouts.

Try this, replacing U+1F4A9 with the actual symbol:
int main() { int U+1F4A9=0; return U+1F4A9; }

That's why I linked to waylandx, not xwayland. I agree that getting rid of X is retarded, and that wayland is not a fit replacement.

There are well-intentioned people who write code using the newest API (as that's usually the right thing to do) thus good programs that require wayland start popping up, that's what waylandx is for. There are also severely misguided folks who drop X like KDE; I don't use KDE myself thus I can't comment on the details.

It looks like X will indeed die due to lack of maintenance, but that day is not yet close. And wayland is not working reliably enough yet even if you don't need remote access.

Perhaps waylandx could help? Might not work for a whole desktop, though.

There are apps and there are apps. Slack can OOM with mere 128GB, it worked stable on 256GB though. On the other hand, there are playable and fun 4K games.

Well, that's why OP didn't call them "osties de tabarnak".