

Just a note: Windows software for controlling hardware is highly likely to assume a)direct access to the hardware (sometimes mediated thorough ancient APIs and assuming the existence of defunct expansion slots) and b) assume meatspace time can be counted using OS timing ticks (which get stretched out as modern VMs timeshare with other processes underneath the virtulized hardware). It is awfully tough to replace them sometimes.
Agree, but this is the ELI10 explanation, not the ELI5 explanation. ChromeOS and Android are both operating systems that look and act very different than an operating system like Debian or Fedora, but all four of these examples use the Linux kernel.