Zerg: Boot a VM instance per request, all in under 250 ms

This is a very interesting development! But doesn't that mean we are merely reimplementing old concepts on a new level? Almost everything we do on VM level we already did on process level: - Read-only VM images are essentially like statically linked binaries, just better encapsulated when they run. - Tiny, fast loading VM images are essentially stripped static binaries with dead code elimination. - Starting those by incoming network request is just like old "inetd" versions started custom handler…

This is really neat stuff. I do not understand though why LING is not open-source already. If you are sincere in your claims for intentions of making it so, why would you wait until it is "mature" before doing so? Wouldn't it mature a lot faster if more people picked it up and tried to use it, submitted defects and even patches?

Isn't this simply an acknowledgement that having an entire OS (at least in a traditional sense) is overkill? I remember a couple of attempts to make the JVM run on bare metal (JavaOS was one if I recall correctly) and I think that, to a lesser extent, ChromeOS, FirefoxOS and company are trying to eliminate some of the bloat that's occurred. The other day I spun up a CentOS6 server on a VM and it required a minimum of 512MB…

"Over capacity The demo is limited to 16 concurrent instances and 2 libvirt connections. Due to these limitations we were unable to spawn a new instance to service your request. Please try again later." Well...that's something, I guess.