I don't know Nature, but the shared-stack coroutine details here are interesting. The fact that C callbacks just work because everything runs on the same stack is a nice side effect of the architecture.
The 10ms timer hack for garbage collection is the kind of pragmatic solution I appreciate. Not elegant, but it works and the latency is acceptable for GUI apps.
Curious about the Linux approach though. Mixing musl static libs with glibc dynamic libs sounds fragile. Have you run into ABI issues with that setup, or does the linker handle it gracefully?
I don't know Nature, but the shared-stack coroutine details here are interesting. The fact that C callbacks just work because everything runs on the same stack is a nice side effect of the architecture.
The 10ms timer hack for garbage collection is the kind of pragmatic solution I appreciate. Not elegant, but it works and the latency is acceptable for GUI apps.
Curious about the Linux approach though. Mixing musl static libs with glibc dynamic libs sounds fragile. Have you run into ABI issues with that setup, or does the linker handle it gracefully?
Will you be providing a Nature MCP and LSP integration soon?