Re:React Concurrent Mode
by tomduncalf on Thursday October 24, 2019 @04:47PM
(#21348987)
Perhaps I don’t fully understand your use case, but would something like MobX solve the problem you describe? Keep your data in stores, components automatically react to changes in them. You could do the same with Redux but MobX gives you finer-gained rerendering (only components who’s data has actually changed rerender)
[ Parent
| on HN ]
Redux already has ways to do fine-grained rerendering. (That's why redux has you give selector callbacks that operate on the state instead of just exposing the whole redux state to components. Redux only re-renders the whole component when a selector callback returns a new value.)
Redux still has to evaluate the selector each time since it has no clue if any of it's depedencies have changed.
That's why libraries like reselect use memoized selectors.