Hi @mcktimo , I'm sorry for my later reply, I was finishing one project. Thanks for your kind words. The composable state is on the way (it's already done and very easily, thanks to Michal Zalecki, too). I'm working on small helper how the message stream can specify which part of the state to work with. I'd be very happy to hear your thought about RxR or even contribute. I'm playing with side project with sockets and the majority of the code on the server and I use RxR there without the React part. I like the RxJS approach and therefore I jump on the idea I read on Michal's blog. So RxR by default is not tightly coupled with React. IoT is still mostly unknown for me but your project sounds interesting.
Thanks David for a sweet implementation and a very clearly written set of documents in github. You are right at the center of what I want to grok. Here in Boston there was recently a meetup faceoff between redux and ngrx that I found fascinating. I love Redux but the ThunkMiddleware seems better for logging than for async.
Dealing with streams of data coming in and streams of user actions seems to be at the heart of things now, more so even than view controllers and components and their associated multimegabyte frameworks. I'd like to be working with a library that does a good job with that and be able to use it to manage my state in React or Angular or just plain old (es6) javascript. I may jump in a little deeper to RxR though I would like a composable state and would like to see RxR stand more alone from React.
I am working in the IOT space, so I can be making stuff useful to me as I build a portfolio of skills that can get me a job in tech. At this point I have a stable esp8266 platform running mqtt to a node broker that pipes it out on websockets. Lots of pub/subs coming in and going out with streams of data from sensors & relays and schedules and state from multiple devices. Ah, now to some frontends...