> We usually see wide-spread vulnerabilities in the middleware like OpenSSH There has been exactly 1 remotely exploitable bug and exactly 1 information leak bu

> We usually see wide-spread vulnerabilities in the middleware like OpenSSH There has been exactly 1 remotely exploitable bug and exactly 1 information leak bug in openssh in more than a decade (I believe the exploit is actually more than a decade old, need to check though), it is by far the most secure daemon ever. It is hard to overstate just how much of an accomplishment that is. NOTHING matches it in security. This is even more impressive given how widespread it's usage it. > We need authority if we are sharing peripherals. I think you'll find that large websites ... just don't do this. The only real purpose of multiple processes on such webservers is administration. > f we are not going to save memory and implement that as a static library ... The reason you want to do this is that the slowest thing in modern processors is context-switching. Going from user-space to kernel space. If you have, say, a networking stack in user space you can avoid such context switching entirely. The speed gains are enormous, especially for webservers. Ridiculous performance in networking also enables many more applications that just won't work without. What do you think about cluster-wide disks, for instance ? SQLite like databases that run against Petabyte-sized files, concurrently, safely. You're just not going to do that efficiently by having it done in the OS.