yep, that's to be expected, this is a very wip demo. I'm implementing exec() support now, so currently only shell builtins work.
Bah. Details, details dismissive hand wave.
It's just minimalism, right? I hear it's all the rage.
Since I map guest threads 1:1 to host threads in JS, and architecture-specific code manages the loading/unloading of programs, the exec syscall is exercising these lies in a way that they're not currently equipped to handle.
What I'm currently doing is improving those lies to the point where exec stops noticing they're lies and just starts functioning as expected.
I opened that on my Android Phone and half expected it not to boot at all. But it does. I have no idea about the state of WASM n stuff, but apparently, it's much more eadvanced than I anticipated. Mind blown.