When To Fetch: Remixing React Router - Ryan Florence
HTML-код
- Опубликовано: 28 май 2022
- Recorded live at Reactathon 2022. Learn more at reactathon.com
When To Fetch: Remixing React Router
We've learned that fetching in components is the quickest way to the worst UX. But it's not just the UX that suffers, the developer experience of fetching in components creates a lot of incidental complexity too: data fetching, data mutations, busy spinners, optimistic UI, error handling, form state, network race conditions, user event interruptions, and all the code that holds it together gets pretty difficult! As we've built Remix, we've gotten a lot of practice leaning on React Router's nested route abstraction to solve all of these problems all at once. Now, millions of React Router apps in production can get the same benefits because we've moved the responsibility of knowing When To Fetch into React Router itself!
About Ryan Florence
Ryan is the co-founder of Remix, co-creator of React Router, and co-founder of React Training.
Event production and post-production by EventLoop. Let's build your conference brand, or take it to the next level. info@eventloop.app 
Наука
Not a React dev but man Ryan knows how to slam dunk a presentation and a demo. The await lever bit at the end of the demo was crisp 👌🏼
he only knows how to break backwards compatibility and steal investments
Wait till you hear Michael Jackson speech, his partner, he is genius!
@@jamesdenmark1396 where?
@@xMrMiagix sorry I thought I send you the link, search for "Michael Jackson Never Write Another HoC", I believe Michael Jackson is the mastermind, behind all what you see! Ryan is the one writing documentation and talking to the press!
Having specific chunks of data to be loaded as per the priority is amazing! And I love the `deferred` option added to Remix :)
Amazing!, Felt great to watch this from my home!
Ryan and Remix always blows my mind!
Ryan, that was your best presentation yet! Thanks for it and looking forward to more of your presentations and for Remix of course. Cheers!
This is groundbreaking honesty, remix has been the biggest boost to my productivity and website performance since I began react 6 years ago. Keep up the amazing work
That was some amazing presentation! Thank you Ryan.
That end demo was insane, I've been using remix for like a month and didn't know I could actually do that
Because it's not out there yet, didn't found it in the official doc. There is just a github action that was commited 3 days ago.
great talk! thanks for sharing all the cool things
Thank for this talk!! Amazing
Super cool!
The developer UX of using just an await as the lever is so elegant. Nice API!
remix is really amazing
beautiful
Ryan talks are always informative and entertaining. My only question is why only now? Don't get me wrong, I'm glad these changes are making it to react router, especially for those of us who can't migrate to SSR just yet, but Angular router allowed a similar approach for years, and it's something that frustrated me when transitioning from Angular 2 to React + React Router. Of course you didn't need React Router if you really wanted to initiate data fetching on a route transition, but it's really neat to be able to do it in a declarative way
lol, when he said all the issue with fetch, i asked, why not use react-query, and boom, he said it
THIS IS HOW you do a Talk .... EVERYONE else, plz take a seat and learn ;) But it helps if you good content and Ryan has 2 amazing content, New React Router AND Remix
It was a very jumpy talk without clear benefits to the listener.
To see Ryan saying Defew when Dethrouple was right there…
Ryan crushed
throwing shade at lee/vercel, oof
I'm a new React Native dev. Trying to learn things. I'm just curious, do Vue/Angular/Svelte guys makes fun of us?
less code. better ux!!
I so hate what they do with the router. 3 version was painful. Now 6. Stop breaking the project. To line your pockets with investments you go to any lengths
Some concepts are hard to grasp.
I think react guys are getting a bit crazy... and start over engineering the front-end end side of software development.
He literally is advocating to use the platform more, and what he talks about, are standard perf metrics, he basically talks 0 react specific stuff here