I was certainly aware of unikernels (on a pretty superficial level) when I started Mu. A shared goal is minimizing attack surface. However, Mu also has a second

I was certainly aware of unikernels (on a pretty superficial level) when I started Mu. A shared goal is minimizing attack surface. However, Mu also has a second goal: minimizing the build time supply chain and making it more auditable. There Mu has more in common with http://bootstrappable.org http://bootstrappable.org which is building https://www.gnu.org/software/mes https://www.gnu.org/software/mes. In service of this goal I've ended up leaving all C behind. As I understand it, unikernels want to let you bring your own application sources, and try to compile it to their substrate. Mu requires you to build your application for it. There's no compatibility with anything beyond the x86 instruction set (and Unicode).