React 19 has a Problem

React 19 has a problem, and that's speed. With a new change to how suspense works, the SAME CODE behaves massively different in how it's executed between 18 and 19. I love what Tk Dodo does for the react community, and turns out, the react team listened to his (and others) concerns.

--- sources

-- my links

[incarnateTheGreat]

This is why they have release candidates. People test it out and find issues like these. Hope it gets sorted.

[idk_who_am_i]

Im not a JS dev but im confused by the logic applied from react devs. WHY would you change the default behavior of a functionality if there are other options or rather it should be the developer that fixes the issue. If you have an expensive component why not make it also be self suspending that would eliminate the need to throw away the first render. Or if that is not possible than why not add an "attribute" to Suspense defining how it handles its children. for example default is "parallel" if you need to you set it to "sequential".

[jamshediqbal]

Fortunately, I haven't used suspense and don't have plans to use in future 🙂

[owenwexler]

So looks like I’m staying on React 18/NextJS 14 for the foreseeable future

[wlockuz]

So much for an "unopinionated" JavaScript "library". React is a damn circus.

[nasko]

"Still recommend preloading but recognize it's not always practical" What do they mean by that? Sure you can preload initial data serverside but if the component is dynamic with dynamic data (like what most of react is used for) you need parallel fetching. I have no idea what they were thinking with this. Am I just missing something?

[algobuddy]

Looks like React 19 is trying out the new "slow and steady wins the race" strategy—except it's losing😆

[JackLdien]

Hey Josh. very basic question :D. What keyboard and mouse you are using? im currently looking for a "good" keyboard for programming and personally i dont like the 100% keyboards

[JollyCoding]

Very curious to see what the solution to this is since they’ve walked back. Seems they liked this feature at Facebook and it helped them.

Easiest way would seemingly be a prop for the method, parallel or waterfall on each Suspense. Default it to parallel.

[jonny]

Does this only apply to client components? Or also RSC with suspense?

[gufoscuro]

"Pretty fast, in the tradition of react" – I wouldn't really remember React for its speed :)

[botondvasvari]

its problem is that its a cyptic shit that shouldnt be used anywhere

[catbb]

“listening to our problem” 😹
i mean they created the problem

[iabhishek]

what coding font you are using josh.... its looking so clean, thanks

[pplytas]

Great vid! I noticed "disk cache" on the first example, doesn't that mean they are returned form the browser cache?

[Gaijin]

Glad we decided to move away from react. Tired of these insane changes. All these 'fixes' and its still significantly compared to Solid, Vue, Svelte.

[ThingEngineer]

Only react would release a ‘mandatory waterfall feature’…

[Tyheir]

Just add a prop to enable sequential rendering. This is where partial pre rendering will come in handy.

[weiho]

const [solution, setSolution] = useVue()

[faridguzman]

vue or svelte is the way. we need to jquery react.