It has, a long time ago when doing serveless became fashionable, and too many realised they didn't want to manage Kubernetes clusters by hand.
So you get a type 1 hypervisor, which technically is like a micro kernel, which then boots whatever else on top including language runtimes, or chiseled containers.
Unikernels ideas aren't much different from some embedded deployment scenarios, with the application, language runtime and OS all linked together into the device firmware.
So you get a type 1 hypervisor, which technically is like a micro kernel, which then boots whatever else on top including language runtimes, or chiseled containers.
Unikernels ideas aren't much different from some embedded deployment scenarios, with the application, language runtime and OS all linked together into the device firmware.
Naturally on desktop computing is another matter.