How Remix solved React’s client state management problem

preview_player
Показать описание

Рекомендации по теме
Комментарии
Автор

Excellent video. The clear title, helpful diagrams and explanation makes the subject very clear. Wish more tech videos were like this.

NiyazPuzhikkunnath
Автор

I feel like somehow remix has implemented its own version of server components that is slightly more lean compared to nextjs.

BeeBeeEight
Автор

The greatest intro to Remix in the history of mankind, you are so good at explaining concepts!

Kisovn
Автор

Excellent video. Keep up your good work for the community. All the best.

opswithtaen
Автор

This was a fantasic video!!! Sad to see that you aren't creating much content as this quality was top notch. Gonna subscribe just in case.

patrickjreid
Автор

Thank you for talking about this topic ❤

maskman
Автор

That's why i love Remix, never have to use any React Context anymore

taquanminhlong
Автор

Great video, you are gifted on explaining things

christosziogas
Автор

The way you explain the remix I wish I found same tutorial on Nextjs wow 🤯

vijayfrontend
Автор

Since I already have the data updated in the local state, what is the advantage of giving a GET again after a POST? Wouldn't it be a waste of resources to hit the API unnecessarily? I'm having this problem with Remix, I've been using the shouldRevalidate function to manage this, but I don't know if it's the best solution. I still miss a local state using Remix.

LeoMiranda
Автор

Could you please do a comparison of Remix with Nextjs?
Like, in this video, I can see improvement made by Remix compared to traditional React + API but I wonder what's the difference with Next.js (it's a popular framework so it should somehow do pretty well in the state management department, no?)
Thanks 😁

EmiliaKaida
Автор

This what nextjs used to have getserverside props. It took me a while to understand and then they changed the data loading and mixed server and client!

al
Автор

How does the loader know that the data it's supposed to load was actually modified by the action? Like, that that specific action modified data that the loader would need?

MichaelCampbell
Автор

Based on how simple you managed to explain the functioning of Remix, it looks far more straightforward than Next.js!

Awesome video bro. You made me want to give it a try!

crisuar
Автор

What about mutations in this page's component that actually affect different pages and not the one we're currently at? Will those be invalidated also? Is there a mechanism to do this?

luizgrocco
Автор

It works exactly like react query... so it makes additional calls to rehydrate after that form post happened ? What if I had 5 more such rehydrations in different places around the app ?

samoniumuziejus
Автор

We still need client state for many other things, we still need Context API to pass this through components

gyros
Автор

How it's different from. RSC's and server actions. I want to create mental picture.

tmanager
Автор

nice content bro subscribed! I HATE REDUX, TANSTACK make more vid like this brotha

abishektamilan
Автор

so if I have paginated data does remix will revalidate all the pages ?

abbaskareem