30 karma · joined April 20, 2019
The version of mach present in XNU is derived from OSFMK, which derives code from UoU's Mach 4 kernel, and from CMU's Mach 3 kernel. It contains improvements related to threading and contexts. It also definitely exists as more than an API. The code that makes up mach is present and identifiable, and thus is "in" XNU. [1]
>Mach, the API, is used (mostly due to legacy reasons).
See above. Abstractions are exposed, and traps are present, but this is not an API clone, it is mach, albeit modified from the original form. It was specifically chosen for its forward thinking benefits. Mach was not the basis for any major Apple OS prior to OS X. There were no "legacy reasons" to motivate its adoption.
>OS X has a Linux-style monolithic kernel (with legacy Mach APIs in userspace).
You do tend to see different opinions on this. Some argue macOS is a hybrid kernel, because it combines elements from a microkernel (mach), a monolithic kernel (BSD), and IOKit. A single address space is shared by the components though, which leads many to call it monolithic. [2]
In Apple's own words:
“M1 also features our unified memory architecture, or UMA. M1 unifies its high‑bandwidth, low‑latency memory into a single pool within a custom package. As a result, all of the technologies in the SoC can access the same data without copying it between multiple pools of memory. This dramatically improves performance and power efficiency." [0]
That consistency isn’t absolute though, rough spots like the boundary between Mach and the BSD components still exist.
The car itself is quite interesting in my opinion, but the untenable range and lack of accessibility doomed it to unpopularity. If Fiat made a reasonably priced version with at least 200KM of range, and high quality cells, I would make it my next car.
[1] https://itunes.apple.com/us/book/kickstart-security-macos-mo...
[2] contact@austinlasota.com