Ok, so at this point we’re getting iOS kernel source releases more often than AOSP drops? Maybe they should rename to i Open Source at this point because they seem to be doing a better job than Google at this now.

It was a good choice for macOS and also works on other platforms.

The same restrictions apply to iPadOS.

I don’t think WebKit would be particularly interested in this.

How is it ad incentivized?

It is actually documented now: https://developer.apple.com/documentation/virtualization/acc...

> Mach is not a very good microkernel at all, because the overhead is much higher than necessary. The L4 family’s IPC design is substantially more efficient, and that’s why they’re used in actual systems.

As opposed to Mach, which is not used in any actual systems

I mentioned XNU below. It doesn’t really count as a microkernel if you, you know, don’t actually use the microkernel part. At least for the 30 years between the FreeBSD collision and the introduction of DriverKit, which does most of its IPC through shared memory (because the mach ports are not efficient enough, I would assume).

Yes, but a lot of other things use Mach messages.

> Undefined behavior-related bugs are permanently hidden.

No they are often found and fixed.

High severity security issues.

But those segfaults will either be memory memory safe or your lines will contain “unsafe” or “unchecked” somewhere.

You can make a fully safe segfault the same way you can in go. Swapping a base reference between two child types. The data pointer and vft pointer aren't updated atomically, so a thread safety issue becomes a memory safety one.

This is no longer allowed with strict concurrency

When did that happen? Or is it something I have to turn on? I had Claude write a swift version of the go version a few months ago and it segfaulted.

Edit: Ah, the global variable I used had a warning that it isn't concurrency safe I didn't notice. So you can compile it, but if you treat warnings as errors you'd be fine.