|
|
|
|
|
by nickdandakis
2427 days ago
|
|
Out of curiosity, how is it not still "rendering"? Do you prefer "start" because it renders a tree of children? But yes, rendering doesn't need to be interrupted. They specifically mention architecture decisions to avoid rendering operations that take too long (debounce and throttle). This eliminates previously necessary architecture decisions while providing a better user experience. How is that solving the wrong problem? Also, this is still the view layer. There's nothing React-specific about data fetching, "complex manipulations" or "event processing". Previously if you had a text input whose output you used to fetch some data and render in a list, you'd use debounce. Now, with Concurrent Mode, you don't have to and can instead use the React API. |
|