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'm currently using Nature to replace Tauri for developing desktop applications, which will allow me to conduct more thorough testing later. Since the linker succeeded in linking, it indicates that all symbols were successfully located. Both libruntime and libuv are highly complex code systems. The fact that the scheduler and coroutine system are already running successfully confirms that all core functions are functioning properly.
augusteo|1 month ago
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?
weiwenhao|1 month ago
Onavo|1 month ago