Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This has thing ring of truth, for me--but do you see virtualization taking the kind of extreme route it'd need to provide more microkernel (at least, like EROS) benefits? A different OS instance for every program? That seems like a pretty kludgy way to do it.


A different OS instance for every program? That seems like a pretty kludgy way to do it.

Kludgy or not, there have been some moves in that direction. People often distribute "VMWare appliances", i.e., a single application packaged up as a VMWare instance; and FreeBSD system administrators often run different services in separate jails.


It also depends on how small the OS is.


Something that's too big today will seem trivially small soon of course.


Those giant 800k floppy disk games, those really amazing 160x120 QT movies at 8fps, remember how colossal Myst was, a whole CD-ROM!


I remember getting 1 mb of memory for my 386. A whole megabyte of memory!

(Firefox is usig 110mb at the moment - I started it about five minutes ago.)


There are other constraints on the size of a program, though. All other things equal, larger programs tend to be harder to maintain, and proportionally buggier. This is completely independent of the cost of memory, the size of processor caches, etc. -- There's nothing like Moore's law affecting the human brain's ability to understand sprawling, tangled code bases.

Also: Bugs in device drivers tend to affect stability much more than in userland programs.


.."Different OS for every program"

yeah it is kludgy, inefficient ... but you are pretty much guaranteed that the setup works, which I think is a lot of the value.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: