That seems like an awful amount of overhead for questionable gain.

Links between, and in between data centers use so called jumbo frames with an mtu of over 9000. Not joking.

Worth mentioning that links at home can use them too, jumbo frame support was rare at one point but now you can get them on really cheap basic switches if you're looking for it. Even incredibly cheap $30 (literally, that's what a 5 port UniFi flex mini lists for direct) switches support them now. Not just an exotic thing for data centers anymore, and it can cut down on overhead within a LAN particularly as you get into 10/25/40/100 Gbps stuff to your own NAS/SAN or whatever.

Does this have a negative impact on SEO or search results in general? I'm clueless about this.

It was a great little device.

It truly was. It just felt good. The UI brings me such positive nostalgia. I was obsessed playing solitaire on that thing.

"There is only a single reference5 dated to 2010 indicating that Microsoft might use a similar approach for its NT kernel."

Googling for it brings up a ton of results.

Not instructions per se. Rosetta is a software based binary translator, and one of the most intensive parts about translating x86 to ARM is having to make sure all load/store instructions are strictly well ordered. To alleviate this pressure, Apple implemented the Total Store Ordering (TSO) feature in hardware, which makes sure that all ARM load and store instructions (transparently) follow the same memory ordering rules as x86.

It is funny to hear sometimes though:

"Apple created a chip which is not an X86! Its awesome! And the best thing about it is ... it does TSO does like an X86! Isn't that great?"

Only some of the time.

I think the last time I ran amd64 on my mac was months ago, a game.

You can self host with Headscale.

If the application in the container wants to add more restrictive rules then it should be allowed to. But it should not be able to mess with the existing rules imposed by the container manager. This would be the ideal outcome.

There is nothing to do here. Landlock already a guarantees that you can't undo rules that were already applied. Your application can further restrict itself but it can't unrestrict itself.

Just need the container manager to not block the landlock system call

I use them on Teams on macOS (and Windows) every day and is the main reason I have them. What you say is simply not true.

It's not open. It's not really about devices. And it's certainly not a partnership.

Open as in "open for business".

So they are using RISC-V already for some embedded cores. For application cores, they are participating in the RISC-V consortium to keep the pressure on ARM and also to be ready for the long game.

I do not expect to see Qualcomm made RISC-V application cores until Android or Windows is completely ported to it, which I think rules out the next several years.