3 ms·
> Why aren't there reactive operating systems (as in OS with reactive API) This is something that's been interesting me lately. I've been working with the exce
by bluejekyll 10y ago
> Why aren't there reactive operating systems (as in OS with reactive API)
This is something that's been interesting me lately. I've been working with the excellent futures and tokio libraries, and I've wondered what would it be like if that was the primitive for all OS interactions?
Basically, imagine a message passing system like Mach, but where the fundamental messages are all futures based. There might be some interesting things possible without holding locks in the kernel.
- phil-opp 10y agoI definitely plan to integrate the futures library in the kernel somehow. We just need some asynchronous things and threads first :).
- bluejekyll 10y agocool! Do you have an overarching design your working off of? Or still too low level?
- phil-opp 10y agoI have some vague ideas for the next posts, but no overarching design. At our current level, there aren't many design choices anyway. It will get much more intesting when we create a threading/concurrency model in the future.