News for hackers. Stuff that matters.
Re:Vue.js: the good, the meh, and the ugly by pcstl on Friday July 06, 2018 @03:47AM (#17469713)
It can be used for that, but it quickly becomes cumbersome. Redux, in my opinion, should be used for complex UI state in applications with complex interfaces where interactions with one part of the UI can change very different parts ("spooky action at a distance", so to say). But it shouldn't be used to keep all your application's state.

Your application's state should live outside of React, and be passed in as the root's props.

Re:Vue.js: the good, the meh, and the ugly by Vinnl on Friday July 06, 2018 @06:13AM (#17470228)
I agree w.r.t. what you should Redux for. That said, if you store application state in Redux, is that nout "outside of React", passing it in as props? (Though not necessarily the root's props.)
Re:Vue.js: the good, the meh, and the ugly by d0100 on Friday July 06, 2018 @04:59PM (#17475053)
I think the opposite.

Redux should have your application state, and any UI state should be in pure React (portals, context, etc).

Redux -> app data React -> UI