im working on a c# micro-framework based on Rx/ES that has a reactor as its primitive. slightly different but similiar to the thoughts outlined in the article,

im working on a c# micro-framework based on Rx/ES that has a reactor as its primitive. slightly different but similiar to the thoughts outlined in the article, nice to know im not the only one thinking at a higher level then the actor. the reactors in my world are have composable IO streams, and can be chained together or with eventmanagers which have backing channels that could be implemented with queues or integrated with akka. in my world though, reactors have child services which do the actual state modification. event processors/pulsers/publishers are the service primitives. i personally though dont want to limit this stuff to the server, and am designing it into the UI using the same API aka what the JS calls call flux.