i was very interested in "NoKernel" even more, and have even thought of an idea of having a kernel running on each core of a CPU with a message passing interface

plan9 also goes towards this direction as well, by creating a uniform socket interface for everything, the next logical step from the unix "everything is a file"

but android also with LXC namespace isolation goes a long way towards this also

and i get it that this is what UFS and ZFS are trying to do to filesystems but really LVM2 does it better overall, you can conceive of a single service that just manages this, and another service that manages permission, like a local version of ETCD

i think it's gonna be a long time yet before we see the end of monolithic kernels though... apple runs on a bsd microkernel and everyone else is running monolithics

i think really it's just about the API differences, it's hard to make a mapping between standard system APIs and the distinctly different way you run things with a no-kernel everything-is-a-service style of architecture... the slowest moving parts of software development are languages and kernels

it's a subject dear to my heart though... kernels and compilers, my two favourite things