> But in reality, I'm betting on hypervisor-based micro OSes as they way to go. We don't need another "app" format, like what Docker/libcontainer and this propo

> But in reality, I'm betting on hypervisor-based micro OSes as they way to go. We don't need another "app" format, like what Docker/libcontainer and this proposal are gravitating toward. We already have one, it's called HTML5/REST/HTTPS. Get that in your skulls people! A tar-ball is an app that serves the directory tree, okay. A POST virtualizes this, like a copy-on-write fork(). Now you have to determine how you virtualize on sessions/user logins/etc. There is nothing in this decade that needs to be done any other way! What you're describing sounds interesting. Is there a way I can read about what you said in more detail? I mean the following: - HTML5/REST/HTTPS can be thought of an app container format? - tarball is an app that serves the directory tree. - POST virtualizes it like a copy-on-write fork() I'm trying to connect it to what I've been thinking: that Javascript is permeating everything, and is like the assembly language of the future, cz everything would be done inside the browser, the OS would only be there to provide hardware (based on the Gary Bernhardt's talk: https://youtu.be/tMEH9OMYmsQ https://youtu.be/tMEH9OMYmsQ).