More like Microsoft's first non Microsoft Azure distro.

This does not explain 100% CPU load these harnesses sometimes exhibit.

UK got involved in bombing Iran even when attack on its base on Cyprus came from Lebanon and would have made more sense to attack the source of the attack if the goal was actual self-defense. That is if we accept the decision was in response to the attack itself, and not to pressure and public humiliation from Trump. Also Turkey also got under missile attack from Iran, and managed to use diplomacy/other means to de-escalate. So not joining the war was a possibility.

Instead of self-defence or helping stop the war, UK helped aggressors in making their attacks easier and deepened/prolonged the war that way, at great cost to the world. At a time when de-escalation was still possible, UK chose to contribute to the war on the side of the aggressors. Who knows why. Maybe they believed it would be a quick war or whatever and Iran would collapse quickly just like the countries UK decided to aggress against in the past like Iraq.

It really bothers me that most of the TUI harnesses are using 100% CPU quite a lot just printing stuff to terminal. Seems ridiculous.

I guess it comes from syntax highlighting/formatting, which is probably not done incrementally, but over the entire so far displayed block of output, recomputed from the beginning for each new streamed in character. Can't imagine anything else causing the rendering to gradually grind to halt when eg. thinking block is open in opnecode and updates get palpably slow as it grows.

Terminal output itself is fast and consumes almost nothing. You can have 60fps terminal apps that update content every frame and that consume almost no CPU time.

If UK/US wanted to be in the in the clear they could have asked UNSC to authorize use of force against Iran.

I guess it's debatable whether the drone attack was proportional. I'd say that attack on clearly military installation of active ally is proportionate. Bombing bases in Britain would be more appropriate I think, since that's where the bombers that attacked Iran flew from and were loaded with weapons.

Results of the promissed probe: https://www.pcpsr.org/en/node/991

Not independent probe, but more information.

OTOH, extermination of population of an enemy city was a direct question in that Israeli poll.

Also on another note, a poll of a population of Gaza does not represent all Muslims. You can easily say that a long term occupied and terrorized population by Israeli Jews, will not be best representative sample of Muslim views on Israel or Jews, even if that population is very largely Muslim.

Conflating views of all Muslims with Muslims from Gaza, lying about the poll and misrepresenting the results to fit your whataboutist views, etc. only shows your total lack of rigor. Nothing else.

You're not telling them to not attack Palestine by shouting "Free Palestine", or anything similar, only that you believe that Palestine should be free, so your comparison is not valid, because it does not contain any hidden assumptions.

They might as well agree with you. They can correctly respond by shouting Free Palestine back at you.

re the second response: Original commenter did not specify exlusivity to jews. So that's my assumption.

Normally websites feature test and just skip using obscure disabled APIs, or more likely, websites don't use those APIs at all or only tracking scripts use it, which are already optional usually.

Problem with CF is that if you want increased security they'll prevent you from gaining it everywhere, even on sites they don't protect, or prevent you from accessing services even the ones you paid for. Browsers don't allow disabling APIs per domain, so you're either at risk everywhere or you're blocked from accessing a lot of things for no particular reason.

CF can't be bothered to feature test.

And BTW, you're not distributing to millions of people as an author of the code.

There are distributions maintainers between you and the world, which can also intervene, and are responsible for what they distribute, build testing on many configurations/architectures/versions - and can decide to revert to protect users, etc. And often do.

FOSS authors themselves can't be expected to keep around outdated systems from 5 years ago just to test build compatibility, in 8 different architectures that someone may want to build their code with.

Very few projects have as comprehensive testsuite as say sqlite. You can never cover everyting, so the beauty of FOSS is that someone will come and tell you and send you a fix for their special system, and now everything is again fine for that one special person, or distro maintainer.

Anyway, seems blown out of proportion. There are a few issues in the tracker, some repeated or obscure. Linux 5.10, really? You want to run frankenkernel from 5 years ago with 30 000+ patches never meant or developed against it applied on top? Good luck. Rsync is least of your worries.

Linux stable, especially these 5 year old trees are mostly a pacifier for companies that don't want to upstream and maintain their drivers and keep up with evolving internal kernel interface. It's nothing good for users, technically.

And I guess if I clone the repo and do a diff against pre-claude and claude assisted state, most of the changes will not be in the actual C code.