Renraku OS: The Way Up
daeken.com
daeken.com
I have thought about a similar system before: install-time verified (and native compiled) managed code, which is guaranteed to only run within its environment, so no need to separate processes into their own address spaces, object store instead of filesystem, orthogonal persistence, network transparent communications channels (in fact, IMO everything should go over some sort of communications channel which can be "rewired" or redirected. Like piping in unix command line, only global, for all apps, GUI or CLI).
Anyway, interesting project!
The idea is that all input and output can be redirected, filtered, scripted etc. I posted a blog post about some of these ideas once, but I'm not gonna post a link :-D been meaning to clean it up for ages, so maybe after I finally get to doing so, I'll share, heh.
(So others don't have to go hunting for it like I did.)
Nice work :)
It has a lot to do with Boo, really, particularly in the compiler. The rest of the OS is fairly similar to what you'd see in other .NET languages (although that has a lot to do with our reflectionless runtime not supporting a lot of the cool Boo functionality yet), but in the compiler the Boo list functionality has made life incredibly easy. The internals of the compiler really look a lot like that of a Lisp implementation; the code is loaded from .NET assembles into S-expression like lists, then transformed repeatedly until it becomes machine code.
No way this could've been done so cleanly in most other .NET languages; my previous .NET compilers can attest to that.