Hacker News new | ask | show | jobs
by GrazeMor 2392 days ago
It's weird how the article mentions that before Suspense there was a waterfall issue. But as far as I understand Suspense introduces the waterfall issue. If you have nested components that need data, the data has to load serially rather than in parallel which creates a waterfall and React devs don't seem to know how to fix this issue.
2 comments

There is no good way to to solve it other than just to use the appropriate tools like react-saga or placeholder state for components.

If you try to make nested components load at the same time consequences can be unpredictable, suspense lacks fine grained control so it is basically a convenient shortcut, same as react state mixins were at the time.

It's like with hooks and other, similar things: It solves a problem in React that's there because of React.