There should be also an embedded (apache)-websever for embedded applications in PHP/Java/etc. MovGP0 06:43, 26 July 2011 (PDT)
Doing It Wrong: You are taking the wrong approach.
The idea is to create an operating system that boots to the web, but you're building it on top of an operating system.
This means you're not eliminating cruft.
You still have to load microcode so you can load an OS so you can load a GUI so you can load a browser so you can load an interperator so you can display content.
If you really want to "boot to the web" you should go straight from microcode to interpreter and skip the OS layer. Make the interpreter the OS and forget about an underlying GUI, application runtimes and backward compatibility.
Get rid of the idea of having an operating system built around a kernel.
In other words, we need something entirely new. If this project is going to be done right we have to throw away the operating system paradigm and create a new foundation that others will rely on for the future.
If you're going to boot to the web, boot the web.
Foxmajik 10:41, 26 July 2011 (PDT)
In regard to "Booting the Web" project, I like the idea os proving support for telephony apps that can leverage HTML5 Api's to make call/send sms and chat over the web. Without the need of using 3rd party services such as Twillio or Tropo..etc.