4 ms·

I really like this. I think the possibilities are multiple. I will try it to test the generic POSIX compliance of my main hobby project. What is the main plus

by program 2mo ago

I really like this. I think the possibilities are multiple. I will try it to test the generic POSIX compliance of my main hobby project. What is the main plus you have over other similar projects or tools like JSLinux? Which preprocessor directives can I expect to have if I need to write custom code when my executable is compiled for Kandelo? What is the reason for choosing GPL instead of MIT or similar?

brandonpayton 2mo ago
> What is the main plus you have over other similar projects or tools like JSLinux? Good question! I had to do some research. Here's my understanding: JSLinux is emulates a complete machine architecture. JSLinux runs in the browser's Wasm runtime, and JSLinux programs run on JSLinux. Both Kandelo's kernel and processes run directly in the browser's Wasm runtime, with the kernel fielding syscalls from processes. Kandelo does not emulate CPUs. Pre-existing software can run on JSLinux, but software must be rebuilt to run on Kandelo. Given the lack of CPU emulation, I would expect Kandelo to be more efficient than JSLinux, but for completeness, it's hard to beat JSLinux's actual system emulation. > Which preprocessor directives can I expect to have if I need to write custom code when my executable is compiled for Kandelo? In general, we intend user software to be buildable by using standard C/POSIX macros with the Kandelo SDK. Does that answer your question? > What is the reason for choosing GPL instead of MIT or similar? We have a mix of GPL and MIT licenses in this project. For software that is not linked with with user programs, we choose the GPL so that folks may build upon our work but cannot make it closed source. Software that links with user programs is intentionally MIT-licensed to avoid forcing user software into the GPL. Here are our brief notes on the topic: https://github.com/Automattic/kandelo/tree/67ad37130e2ba4c11c037153e8e544f6df5a13ff#license https://github.com/Automattic/kandelo/tree/67ad37130e2ba4c11...

by program 2mo ago

brandonpayton 2mo ago

> What is the main plus you have over other similar projects or tools like JSLinux? Good question! I had to do some research. Here's my understanding: JSLinux is emulates a complete machine architecture. JSLinux runs in the browser's Wasm runtime, and JSLinux programs run on JSLinux. Both Kandelo's kernel and processes run directly in the browser's Wasm runtime, with the kernel fielding syscalls from processes. Kandelo does not emulate CPUs. Pre-existing software can run on JSLinux, but software must be rebuilt to run on Kandelo. Given the lack of CPU emulation, I would expect Kandelo to be more efficient than JSLinux, but for completeness, it's hard to beat JSLinux's actual system emulation. > Which preprocessor directives can I expect to have if I need to write custom code when my executable is compiled for Kandelo? In general, we intend user software to be buildable by using standard C/POSIX macros with the Kandelo SDK. Does that answer your question? > What is the reason for choosing GPL instead of MIT or similar? We have a mix of GPL and MIT licenses in this project. For software that is not linked with with user programs, we choose the GPL so that folks may build upon our work but cannot make it closed source. Software that links with user programs is intentionally MIT-licensed to avoid forcing user software into the GPL. Here are our brief notes on the topic: https://github.com/Automattic/kandelo/tree/67ad37130e2ba4c11c037153e8e544f6df5a13ff#license https://github.com/Automattic/kandelo/tree/67ad37130e2ba4c11...