Interesting will be to see that thing in action for a modern web-application with tonns and tonns of async operations/business logic and possible SSR requirements. Not sure I like a lot concept with rerendering content "without" React, which in the end can create a mess (who is in charge here?). Can theoretically be a rendering 'conflict' then? I agree with one of comments here, that this is a huge step back/out from the common FLUX approach, but sometimes I indeed think that redux-react ecosystem started to be overcomplicated and not performant. Rerendering whole React Tree just because of a tiny change was always my concern. So in general - sounds interesting and worth a try! Thanks.