technically doesn't come by default with Linux (the kernel) anyways
> no display support
can be configured out. I'm pretty sure you can even configure out the whole TTY subsystem if you want, so you can't even use a serial port to debug your madness.
> no printer support
who still uses parallel ports? for anything else (except usblp which basically never works) you need CUPS anyways
> no hot plugging support
last I checked, hotplug is mandatory on x86 (but only for certain components, so you could configure out say USB support if you wanted)
> few drivers
sure, you can compile your own kernel if you want
> no battery management
I don't really know what "battery management" means.
> The OS underneath ought to be simple enough to be installed for the life of the hardware.
you can already try this with Linux. then you run in to problems like "what happens when there's a vulnerability in Xen", because https://marc.info/?l=openbsd-misc&m=119318909016582.
I assume he means "power management" (i.e. ACPI on x86). You can run the system without taking control of the ACPI hardware, but this is a terrible idea. It'll affect your ability to run the CPU properly, even assuming you don't care about power usage (and large server deployments sure do!). Not to mention all the nasty bugs and problems you'll run into because the hardware wasn't designed to run for long periods of time without ACPI active.
I know it's almost mandatory for the base machine running on actual hardware, but given that most of the servers we use now are just virtualized, how bad would removing ACPI support be? Also, would it be useful to remove that?
Also I remember reading something about some hypervisors using the guest's decisions with regards to CPU power states to inform the hypervisor's setting of the same on the real hardware. I'm not sure if this is implemented in mainstream hypervisors, or if it's really useful, but that's another thing you'd lose.
There are benefits to using the same components both inside and outside of the VM, just as there are benefits to using the same codebase bother on the server side and on the client side. There's less code to maintain, and you don't have to spend time worrying about compatibility.
I wouldn't mind the small inefficiency of carrying extra drivers and subsystems inside of my VM if it helps make my stack as a whole more uniform and predictable. We really don't need yet another Linux distribution.
I jest but as an industry we do seem have an almost metronome-like tendency to lurch from one thing and back.
For example, all JEE containers allow for sharing libraries among applications, and they can be running bare metal for what I care.
I can even control in which order they get loaded in each application.
The real "operating system" is the container orchestration system.