here are my thoughts. there once was chromeOS, which was the idea to build an OS as a browser. more recently exobrowser is bootstrapping chrome via node. which

here are my thoughts. there once was chromeOS, which was the idea to build an OS as a browser. more recently exobrowser is bootstrapping chrome via node. which means you can expose rendering methods. if you compare that with what different OS layers does, you might as well use the exposed rendering methods to expose your local data and services (=KDE/Gnome). so I would study Wayland for this first. there you learn render stuff to the screen speaking to the kernel. it's 100x easier than X11. I don't know KDE/Gnome internals but I would assume with Wayland some of it can be rebuild now (?). so you could then basically script the GUI perhaps in quite new ways. if you compare that to what the exobrowser is doing you get the picture. so coreOS => Docker => wayland. network servers are booted up from remote, so the network part is becoming more core. virtualization/containers allow for different isolation of processes which speak to the network. then you have a thin layer of display. so for example imagine hookup a oculus and having that as a kind of OS, see this demo http://www.youtube.com/watch?v=_FjuPn7MXMs http://www.youtube.com/watch?v=_FjuPn7MXMs the future is going to be cool ;)