Or for container based distributions where it is basically there to provide the minimal set of services to run containers, and any other kernel would do, it is only a matter of convenience to ping back on the Linux kernel.
The monolithic kernel folks just haven't noticed it.
I know may be by sheer number of users most people use them in the cloud or for development but some of us do actually use linux on our everyday machines.
> GP: development
Probably yes?
Even foregoing development scenarios, containers can be used for everyday Linux tasks with things like toolbox/distrobox (which do support GUIs).
Then there is the whole IPC taking place across containers with much slower APIs and heavier context switch states.
The two remaining ones are worse than any micro-kernel API call in performace.
[1]: https://docs.docker.com/engine/reference/run/#ipc-settings--...
AWS overwhelmingly uses Linux/KVM, not any type 1 hypervisor. There's a few leftover Xen systems, but those are legacy; you get KVM if you provision a new instance.
That is the beauty of hypervisors, just enough abstraction for a portable language runtime.
Right. Which means they're not microkernels. Which is my point.