One thing to be careful with these models is that you're moving the burden of maintaining libraries to the application code. So instead of updating packages an

One thing to be careful with these models is that you're moving the burden of maintaining libraries to the application code. So instead of updating packages and what not, you rely on the developer to update the libraries and reship. Sure its not far from today's model if the dev has to ship the whole container, but it also makes it even harder. How do you know if you have lib x or z when it's sometimes just dropped among a bunch of files? I think it's much worse. it hides the problem and makes it difficult to detect. I'm suspecting kernels will slowly converge toward plan9-like functionality instead. It makes more sense. It's faster, more efficient, simpler. The main barrier so far has been portability - but with more and more apps being written on very portable languages (python, Go, C#, ...) its becoming easier.