brandonpayton

> The stdin and stdout that the commands use actually have multiple channels, with html, json, and raw output possible. Commands can provide different output to each channel or just one.

This is pretty interesting!

> The contents are auto downgraded to whatever the reader can handle. So a program can actually output an <img> tag but if it is piped to something that can't handle html input it will receive it as text of the html source.

Like a stream of typed entities? This is a neat idea and one I'll need to digest. What kinds of ways do you use it?

> If it had hooks for allowing the host environment to manage operations for some file descriptors then my environment would be able to assemble something that looked like stdin and stdout to the running process.

I think there should be a protocol for custom mount types and made a Kandelo issue for it [1].

> There's obviously a lot more going on for things that do graphics. Something that hid KMS stuff inside an iframe doesn't seem like it would be impossible though.

We have Linux-style framebuffer support and exploratory devices for direct rendering. IIRC, all target a <canvas> context from a worker, so it seems like there should be a path to rendering to one embedded in an iframe.

Hopefully we can make running these kinds of commands easier as the project progresses.

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.