XMOS is still keeping the Inmos dream alive, more or less!

This is also my recollection.

Small nitpick: malloc is not a system call.

Good catch! We will fix this in the next version and change it to brk/sbrk or mmap

That jumped out at me too. It stood out amid the (excellent) performance model validation.

And Mach 3 vs 2.5. And a 4.4BSD (well, *BSD) user land, although in fairness the original, never released NEXTSTEP 4.0 also had this.

Another approach is swift-java, which uses Swift macros and also supports Panama.

https://github.com/swiftlang/swift-java

Panama will probably never make it to Android, given Google's behaviour on updating Java support.

That’s sad. One of the first pieces of (serious) software I wrote was licensed by HP for bundling with it. Didn’t use HP-UX a lot but it’s a pity we’re asymptoting towards a Unix monoculture.

Sequential doesn’t mean reentrancy safe, something which has bitten me a few times in Swift concurrency.

Not really! AES67 is essentially RTP with a PTP derived media clock. Connection description uses SDP and unicast signaling uses SIP. Just like VoIP.

Also I imagine TDM was first used in telephony.

Yup, similar for audio stuff.

Oddly Swift appears to support QNX but there’s not much information about it.

https://github.com/swiftlang/swift-testing/issues/868

Does this mean QNX supports at least some of the Apple software?

Not at all. Swift is just a programming language.