The biggest issue is that people daily-driving Linux writes much code that is hard to compile/run under other operating systems, if more people are daily driving we could hopefully end up with less "works on my machine" code.

Gee, I'm sure glad that Trump made the world safer by cutting WHO support. /s

The FreeBSD kernel is damn stable and many who's gotten into it prefer managing servers since it's usually fairly stable as a base OS.
Web-servers has historically been an easier propsition on it also (fast sendfile support).

The biggest issue is usually developers on Linux having a "works on my machine" mentality so much software requires a bit of porting effort due
to different headers and some minor differences in syscall/signal behaviours. (90% of the time you can add an #ifdef __FREEBSD__ or similar for like 5 lines of code out of millions).

Two things have made it worse in recent years though:

1: Docker itself required a fair bit of special Linux-isms that went way beyond what FreeBSD's API-compatibility layer could manage.
There was 2-3 attempts at a more "native" FreeBSD experience, but they didn't pan out or mature enough due to the above.

The way forward though seems to be the Podman project that seems better architected with less Linux-isms and the bhyve VM
(similar to the osX Xhyve port) running a core VM that Podman can fork containers out off.

2: Faster virtual machines (JIT compiled), while the core ABI iirc is the same there are some small differences in memory mapping,etc
that seems to trip up VM's sometimes and without FreeBSD specific maintainers it's support is often left behind.

Even then some package systems contain binaries that are often Linux only (This is an issue with .NET Core for example),
Dotnet Core now runs on FreeBSD but since the NuGet system includes precompiled binaries it can still be an issue.

Conversely, node/npm that works from source is sometimes better but instead runs into issues where people's native modules fail at compiling.

I'm still hanging on to FreeBSD as much as possible, but for some scenarios I'm considering Linux (or Podman maturing).

Like the RH article mentioned, inodes are only unique per-filesystem, having a mount-point in the middle of a hierarchy where someone will run tar or find might mess up the results.

Even then iirc some networked filesystems like Samba might not even expose inode information. Dunno if Linux makes up inode numbers from pathnames or it's just the same? (I remember reading about it being a contentious issue back in the day to allow Samba mounts due to the lack of inode numbers, I guess the tide has turned since)

Counterpoint:

The lid creates underpressure and thus reducing suction when flushing, so the number of times you get stray-floaters after flushing goes up
(those are mostly only discovered by the next person who lifts the lid because the flusher never checked).

Yep, I'd guess they'll get it within 5 years if there isn't any bad side effects discovered.
(The DDT prize really changed how they've handed out some of the prizes, but this is high profile enough that they won't want to miss it either)

Not necessarily, if supply is an issue an another vaccine is unpopular there might be people that just take the easiest route.

For example in Denmark the use of AZ and JJ was discouraged nationally and a focus was put on mRNA vaccines, but as the stocks freed up and the govt wanted more coverage they allowed for younger persons to take AZ/JJ ahead of the planned schedule AGAINS'T the medical communitys wishes.

Now these people that got it early might now be considering taking later shots of mRNA vaccines to get better protection for Delta as they become eligble in the regular queue.

Klarna is mostly a tech company (atleast historically), started out offering payment backends for E-tailers like Stripe. The bank thing is a more recent development due to the way they make most money nowadays (chasing customers with late-fees).

In addition, being in Stockholm they were also one of the first adopters of Erlang outside of Ericsson with all early backend development done in Erlang(changed now though).

So relevant? Partially by the company yes but also in addition to the failure itself (that I think was covered here earlier) that seemed to be some kind of weird cache key mixup issue.

That kinda has been the thinking of every military planner going on the offensive, WW1, WW2, Korea war, Afghan wars,etc but reality has often complicated things leading to prolonged conflicts.

Now sure, the complex supply chains needed to build an advanced air-force might be destroyed quickly but short of an invasion (That will lead to tricky insurgency fighting) an attacked major country will probably have enough resources left to start producing AA weapons (not counting that there is probably far more advanced AA weapons in existence than there is aircraft for any power) causing an attacking air-force to be worn down over time (think of the Battle of Britain).

The Iraqi war was the first chapter of modern air superiority but the subsequent Serbian conflict showed that even if being initially suppressed, the Serbians did show that a technologically inferior party will find ways to shoot down aircraft (That are expensive to replace) and with the land mass of the US or Russia (partly China) then those parties will find ways to make attacks far into the center of their territory tricky, short of using Nuclear weapons, leaving an area where they could restart production of weapons.

"We believe the cause of this incident was a misconfiguration of the routers at a local third-party internet service provider." - Maybe the Russian censorship of Twitter had unintended side-effects? Iirc parts of Twitter are hosted at Google so it certainly seems plausible.

Gotta say that it reminds an awful lot of Asimov's old short story "The Dead Past"

Not only that, the release schedule was just stupid. I was holding on to my SE awaiting another small phone and when the new SE wasn't small i just caved on getting a "larger" device.

Had the mini been known when the SE2 was released at least I would've waited (and bought a more expensive device). And i know of other people with "small hands" that were also holding on to their old SE phones.

Sure this is entirely anecdotal but people with smaller hands that actually want to use their phone with one hand exist and the SE was just right for us. And even at 5% of Apples sales this is still quite a large chunk of money.

More importantly than bandwidth, LATENCY! Many complain about pointer chasing with languages like Java,JS,etc that easily happens due to spread out pointers leading to latencies compared to the speeds of dense array processing in languages like C/C++,etc. At the same time i've been a bit curious about Apple JS performance on their phones beating or being on par with modern desktop PC's. (See DHH's twitter) If the on-chip ram reduces latencies significantly then memory bandwidth or even clock speed issues might just go out the window for most everyday tasks (and many tasks that require dense array processing belong on GPU's anyhow and with zero-copy between GPU-CPU it could just run through it) Too bad about the small memory sizes that are possible so far but hybridizing or using this is cache might be in the works. (Worksets above 16gb where pointer chasing is involved probably isn't too common)

Not really kept track of him (Did he axe climate research?) but not creating new stuff might actually be a good thing as IMHO it seems like NASA has been flipflopping on designs and goals and not really finishing the big project and seems to be somewhat on track for the time being.

Minecraft actually seems to have a minor resurgence lately thanks to some update that apperantly added interesting stuff, and they do try to recruit interesting talent there.

The downside is that well... as with many other one hit wonders it seems like slapping the hit brand onto random experiments hasn't yielded another hit so far, so the entire studio still relies entirely on Minecraft not turning to shit.