Recently it was announced that Google was developing an operating system that could (according to some) potentially compete with both; Google Chrome, and Android, which are both largely driven by the Linux Kernel.
The reason is speed, but perhaps not the way you currently look at speed related to computers or operating systems.
The Linux kernel – Since 1991 the evolution of Linux (Programmed in C) base kernel code that runs; servers, desktop systems, and more recently embedded systems, has remained powerfully rooted in one desired outcome of that evolution. “Make the hardware understand the software and the input/output devices, then feed all of that through in a way that usually doesn’t start fires.”
In short, most kernels are designed to parse some code and user input into binary to run through your “fancy processor” and they do all of that in a preprogrammed order.
Essentially everything above the “kernel” is mostly just an arrangement of interpreters, windows managers, compilers, etc that break programs into “consumable chunks of code” that get sent down through that kernel, (again in a rational order.)
Unless we’re talking about an RTOS or “Real Time Operating System” like QNX or in this instance Google Fuchsia.
No matter how much we’d like to call any RTOS, “Real Time,” we are actually talking about removing layers of abstraction from the kernel that parse codes as they are requested by throwing the order of parsing out of the equation. Pressing enter doesn’t suddenly make a computer behave that much more quickly simply because you told a machine to behave differently, although to be fair an RTOS does actually behave a bit more like an electric typewriter and that’s the general idea.
QNX – While Unix like, is an RTOS and uses microcode somewhat differently than an ordinary PC in that it’s almost designed to have a limited range of use, i.e. ATM machines, 3D protoyping, Automation technology, Avionics, and even Robotics. Imagine how long a Terminator style robot would take to pre-plan a slapfight and you’ll start to understand that it probably would have used an adaptive RTOS for most of it’s motor functions, and a Linux type scheduler for it’s brain.
That is just an example of two very compatible tools that should be used in conjunction for anything similar, i.e. piloting a drone but on a scale that it’s flight control surfaces need independent embedded systems… those would be RTOS type systems.
Most likely Google needs to create a specialized version of this type of operating system for implementing their designs, rather than reinventing them. If they have a robotic toaster in the works, it won’t need this OS.
(Unless it flies, tracks your movements, and shoots toast directly into your mouth.) <— Actually that can probably be done with Linux embedded systems as well but it might take longer to teach it than a brand new built to order OS.
So while it may very well may be slated to have a desktop version, laptop version, mobile version, and embedded version, you’ll not really see the true potential of it until the flying toaster version because that’s how RTOS rolls, or RTOSes Roll?