[mathgladiator]

Keep it up, I love new OSes.

My dream is to write a cloud programming language that compiles high level code to a low-level kernel and deploys. I abhor waste, so efforts like this are a great start. I look forward to more!

[icey]

Some years ago a friend of mine and I built a "self-propagating" system to speed up server deployment. Every server inside the datacenter would periodically look for hardware it wasn't previously aware of in its subnet, and then it would try a few known exploits to root the box, and run our shim. The shim would install all the software we wanted on the box, apply patches, reboot the machine, bring it online and register it so that all the other machines knew about it.

It was kind of a fun experiment, but in the end didn't save us enough time to maintain it for very long - the real time sink was getting the hardware bootable and into the datacenter to begin with. (This was pre-"cloud" days, I guess if we were doing it again now we might have used it for a little longer.)

[there]

http://github.com/avsm/mirage

[pedrocr]

> My dream is to write a cloud programming language that compiles high level code to a low-level kernel and deploys.

I'm curious as to what you want to gain from that compared to running a custom compiled Linux kernel with your program as init or as the only running process.

[mathgladiator]

Nothing from an engineering standpoint.

http://en.wikipedia.org/wiki/Art_for_art%27s_sake

[logicalmind]

Your dream idea will work for cpu-bound programs but it seems the majority of applications are bound by factors other than the cpu. The waste frequently comes from waiting for I/O to complete.

[mathgladiator]

That's exactly true which is why I'm working on understanding IO bound applications (my current research: http://github.com/mathgladiator/node.ocaml )

[c00p3r]

don't reinvent the wheel - hack a Scheme. ^_^