@0xAndy
This is the first time I've felt like leaving the React ecosystem in almost a decade.
@jazzmaster89
Great video. This is completely asinine though by the react team. Imagine how many devs aren't going to be aware of these nuances. What are they thinking?
@mertdr
Great content Jack! I think passing fetch results to another component in order to fix “use”hook’s behavior ends up with unpractical decoupling. And these examples don’t even cover refetching and loading state (currently loading through suspense), which probably would require passing other props as well. I guess React Query will continue to shine for fetching data in React 19 as well.
@mueslirieger
Man, I love your videos. Even though I'm currently more focused on development with Nuxt, I usually use your videos to keep up to date on React stuff, and I gotta say, your videos never disappoint. They are so informative and your presentation is neither distracting nor boring. This is simply the best React content there is imo
@blizzy78
I love these in the weeds videos, keep em coming
@o_glethorpe
0:30 I thought React 19 was created to solve exactly this kind of problem. They just can't make React not suck. Will try again when 20 comes out.
@rodrigorb2630
Man, I feel for folks trying to launch and maintain courses on React in 2024
@ryandsouza2962
Amazing vid! This make s my decision of going with Astro and HTMX even stronger
@fexxix
From this video I have learned that react-query is here to stay for a very long time
@MrJettann
Awesome as always, Jack! Will your course be available any soon?)
@AsifMushtaq-k6b
How long we are going to learn React? Is it's a matrix lol
@versaleyoutubevanced8647
I'm some of the folks that like these type of content ❤
@derekpowersblight
I "Promise All" these work :P
@SebaKerckhof
Remember how the promise of react was that functional components would be easy to reason about. It's one giant clusterfuck of a footgun by now.
@elraito
I cant explain exatcly why but with all these intrinsic sort of "rules" you need to know just keep muddying react. When thet introduced hooks i wasnt able to see why it was necessary at first but started to like the patterns on time. I hope the same is happening now when it finally "clicks" i eill actually like the new rules
@adityatiwari811
Good one. Thanks!
@bigmistqke
I don't really understand the design decision behind why use is sequential. Why wouldn't they simply collect the promises during mount and then resolve them in parallel 🤔I suppose they can't attach it to the fiber because it's not really a hook? But then maybe keep the hook rules for use? Add a dependency array if u want to conditionally fetch, tanstack query style?
@SD-uf4ng
Hi jack if we hosit the promise in same component using a state and use it in Use hook it is still fetching infinitely in React 19 stable release
@thisweekinreact
Interesting and surprising behavior 😮 Couldn't this be considered a React bug or temporary limutation? Is there a reason for reexecuting the useState init? Looks like the previous/initial result could be reused.
@amirrezam75