What are your thoughts on using stateless function components + redux as the way to maintain UI state?

[jimbolla]

Would you do it? And if so, how would you shape your state to separate UI state from model state?

[gaearon]

Tough question. I wouldn't go so far as to put all state into Redux store—just what feels natural and simplifies the surrounding code, predictability and testing.

To be honest I have no idea about the future of managing state. I don't think setState() is the right API but I'm not sure about alternatives either. I think we might have gone too far into the “externalize the state” direction thus losing the colocation. Maybe React can provide a better state API that would yield the same benefits as Redux gives you, but with colocation.

I'm really interested in “fractal architectures” like Elm Architecture and Cycle's Nested Dialogues as Andre Staltz describes here. I wrote React Elmish Example to try to better understand Elm architecture myself.

The future is fun and