Hi! I have a few questions: 1) What are the benefits of the reactive operating systems? Do you have any example use-cases that this does better than tradition

Hi! I have a few questions: 1) What are the benefits of the reactive operating systems? Do you have any example use-cases that this does better than traditional approaches? 2) Do you find this related to functional reactive programming at all? 3) Since this is a model of concurrency with eventual consistency, do you see it benefitting from eventually-consistent OT or CRDT data types? I am asking because I am working on what might be a related model: https://braid.org https://braid.org and https://stateb.us https://stateb.us. We are building a "distributed state abstraction", that we envision will end up in three places: a) HTTP will upgrade from a state transfer to a state synchronization protocol b) Applications will be separated into UIs on top of a "web of state" (see https://stateb.us/static/statebus-demo-3-31.mp4 https://stateb.us/static/statebus-demo-3-31.mp4 ) and transition from web apps to app webs c) Operating Systems will replace file systems with state systems; where local variables in memory can persist to disk without explicit read/write calls, and can be read/written across processes without programming overhead. So I am asking these questions because I wonder if we are all looking at the same programming abstraction, but from different perspectives!