25 ms·

> As the author of Redux I can assure that it’s not designed for — or capable of — the providing thee features described on this page... Hope that makes sense.

> As the author of Redux I can assure that it’s not designed for — or capable of — the providing thee features described on this page... Hope that makes sense. Sure! Seems like we are talking past each other (these problems being waterfalls and data races and the examples coming from https://reactjs.org/docs/concurrent-mode-suspense.html https://reactjs.org/docs/concurrent-mode-suspense.html).

danabramov 7y ago
I could write a separate comparison of Redux vs Suspense, but it wouldn't make sense to do in React docs because React docs are about... React. Otherwise we'd have to write a comparison for every popular state management solution, which is a lot. If I were to write this comparison, the gist of it would be "Yes, you can solve waterfalls and races, but what's your answer to features on this page: https://reactjs.org/docs/concurrent-mode-patterns.html" https://reactjs.org/docs/concurrent-mode-patterns.html"
acemarke 7y ago
Right, and as a _current_ Redux maintainer, I can also assure you that Redux does nothing to solve those problems :) Redux is simply a synchronous external data store. It does nothing in regards to how you fetch your data. While React-Redux does trigger UI re-renders when the store is updated, we rely on React's own scheduling capabilities to handle actually updating the UI. So, no, Redux definitely does not solve the patterns described in those docs. I'm hopeful that we may be able to eventually build some integrations between Redux and Suspense at some point in the future, but frankly we've been waiting for actual docs and examples of how all this stuff is _meant_ to work. Conveniently, we now actually have some (thanks Dan!), but it's still going to take a long time to absorb what the APIs are and what techniques may be possible.

25 ms·

> As the author of Redux I can assure that it’s not designed for — or capable of — the providing thee features described on this page... Hope that makes sense.

by kansface 7y ago

danabramov 7y ago
I could write a separate comparison of Redux vs Suspense, but it wouldn't make sense to do in React docs because React docs are about... React. Otherwise we'd have to write a comparison for every popular state management solution, which is a lot. If I were to write this comparison, the gist of it would be "Yes, you can solve waterfalls and races, but what's your answer to features on this page: https://reactjs.org/docs/concurrent-mode-patterns.html" https://reactjs.org/docs/concurrent-mode-patterns.html"
acemarke 7y ago
Right, and as a _current_ Redux maintainer, I can also assure you that Redux does nothing to solve those problems :) Redux is simply a synchronous external data store. It does nothing in regards to how you fetch your data. While React-Redux does trigger UI re-renders when the store is updated, we rely on React's own scheduling capabilities to handle actually updating the UI. So, no, Redux definitely does not solve the patterns described in those docs. I'm hopeful that we may be able to eventually build some integrations between Redux and Suspense at some point in the future, but frankly we've been waiting for actual docs and examples of how all this stuff is _meant_ to work. Conveniently, we now actually have some (thanks Dan!), but it's still going to take a long time to absorb what the APIs are and what techniques may be possible.