I love your idea!

[piranna]

Honestly, youar architecture seems to be almost perfect, congrats! :-D I decided to make NodeOS compatible with current apps, but if you could be able to make jskernel compatible with Node.js, I would be more than gladly to use it as the NodeOS kernel :-)

By the way, the architecture schemes are better done down-up, since they are stacks... ;-)

[streamich]

By the way, the architecture schemes are better done down-up, since they are stacks... ;-)

That implies stacks grow upward ;-). But I agree they would look better if I drawn then down-up.

[piranna]

That implies stacks grow upward ;-)

Yeah, the stacks always grow upward, specially if things are build on top of other layers, and in last instance on top of the hardware ;-)

[ahmed-masud]

I concur! This is a fantastic idea, I'll be trying my best to contribute.

[0bOne]

I am researching ideas for building a non-nix non-windows self-contained for-virtualization web/database server using the fewest languages possible.

I gradually came to the conclusion that a good approach would be an exokernel based on something like Google's V8 engine. Node.js has too much functionality to match the 'absolute lightest' design constaints, of my project, but this project is very intriguing.

I am interested in how far this project has come, whether it would be a suitable starting place to save me re-inventing the wheel.

Do you think your project would be a good match? How far along is it? Is it worth me contributing to this project or starting from scratch?

Thanks in advance David

[streamich]

@dp68 I am continuing development in https://github.com/streamich/bamboo from time to time.

Things that are done:

• I have runtime bindings for Node, Duktape, and V8 (see bamboo-runtime-*) those basically implement feautres of libsys, that is all Bamboo needs to run. The most minimal version of Bamboo should need only libsys.syscall().
• libjs — is like libc in C, but in JavaScript.
• I have basic event loop with timers implemented (which supports ref and un-ref queues and micro-tick queue), but it still needs self-pipe integration with thread pool.
• I have asyscall a lib that creates a thread pool from JavaScript using Assembler.js, for asynchronous file system operations. It basically creates process.asyscall().
• I have most of the file system module implemented
• Other small things from node core are implemented.

Missing parts:

• The biggest missing part is networking, I got basic prototypes working, but not much. Basically, dns, udp, net, http modules need to be created. When I will have time I will work on them.
• Signals are not implemented but can be done relatively easily.
• Many other things still need to be done...