Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The problem here is that Apple themselves have problems with their kernel-space code.


True, the point is that they are taking multiple paths to make macOS/iOS more secure and (we already discussed this to death), more micro-kernel like, even if not pure.

A kernel with Apple only code, is more stable and secure than letting everyone to the party.

Every little piece of the puzzle helps.


Yep. It does too much and it's still stuck in he 1980's. If you want security: a formally-verified microkernel that doesn't do much but memory mapping, IPC, and context switching. Everything else needs to be running either in a VM like BEAM or formally-verifiable, statically-compiled, safe "userland"-ish binaries.

Going beyond PNP and ACPI, per-OS hardware drivers could be made unnecessary if vendors provided "ACPI"-like APIs that exposed standard, introspectable functions and data structures to the OS in a unified way independent of bus and architecture, i.e., a GPU, a block device, a serial port, a sensor. A universal "IOKit" would required less integration and development effort for all to support, and every OS would get support for free.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: