any downside? about redux-fly

[MrEfrem]

Hi. I don't used it in real projects. Now I very busy and haven't a time to work on it.

[qbolec]

Hi!
I'm learning Redux, and spent last week searching for a solution which would make writing reusable components, which depend on each other, etc.
I've found your project through https://github.com/slorber/scalable-frontend-with-elm-or-redux/tree/master/redux-fly-mrefrem/src which seems to be one of the simplest implementations in that repo. Way simpler than a 7-files long implementation of a boolean switch https://github.com/slorber/scalable-frontend-with-elm-or-redux/tree/master/redux-saga-jaysoo/src/theButton at least :D
I like the idea of keeping all the stuff in one file.
And the idea of keeping all the state in one place.
And the idea of having otherwise stateless components, that is jsx expressed as a function of the single source of truth (I still don't understand how people can be so calm when using React's this.state and this.instanceProperties https://stackoverflow.com/questions/45060233/in-what-situations-react-creates-a-new-instance-of-a-component. And I have even more problems comprehending how people deal with having a separate redux state on top of that).

[MrEfrem]

@qbolec you should to learn official docs: https://facebook.github.io/react/tutorial/tutorial.html, https://facebook.github.io/react/docs/lifting-state-up.html.
I use mix React state with Redux state. React state in branches of components and Redux for separation of data between branches, iframes.