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!
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 😁
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?
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 ?
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.
Remix is way slower than react, I've worked in both framework and trust me I was tasked to migrate all the code from remix to nextjs ended up in faster initial load time with better response time
React sucks. Can't be fixed. Just use a better tool. It's like building a broken layer of abstraction and building another layer to fix that and another layer... Sometimes you need to say I've had enough of this, let's start over with something new without the inherent and needless complexity. It's only smart to do so.
@@j.r.r.tolkien8724 you said "just use a better tool", I understood that you prefer another framework other than react, if that's the case what do you suggest ?
I feel like somehow remix has implemented its own version of server components that is slightly more lean compared to nextjs.
Excellent video. The clear title, helpful diagrams and explanation makes the subject very clear. Wish more tech videos were like this.
The greatest intro to Remix in the history of mankind, you are so good at explaining concepts!
Excellent video. Keep up your good work for the community. All the best.
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.
That's why i love Remix, never have to use any React Context anymore
Too bad Remix is gone, React 🐑 😂
@@j.r.r.tolkien8724where?
@@j.r.r.tolkien8724 What do you mean by gone?
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!
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 😁
Thank you for talking about this topic ❤
Remix is just underrated ❤
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?
We need more videos like these!!!
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 ?
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.
Useful video, thanks!✨
Thanks, Great explanation.
How it's different from. RSC's and server actions. I want to create mental picture.
It’s more like old school PHP with a controller / view with file based routing
why is it better than using react lazy components ?
so if I have paginated data does remix will revalidate all the pages ?
Wake up babe another framework dropped claiming to fix yet something in React.
On a side note interesting will try this with my new POC
Nice explanation
Hi great video. Can you provide the colorful remix logo to download. Thanks.
Do remix vs next js next
Library number 109,877 that fixes react state 🤘
Remix is amazing
I love you
It's NOT React VS Remix. It's Remix VS Next.js. You're missing the point completely!
Remix is way slower than react, I've worked in both framework and trust me I was tasked to migrate all the code from remix to nextjs ended up in faster initial load time with better response time
React sucks. Can't be fixed. Just use a better tool. It's like building a broken layer of abstraction and building another layer to fix that and another layer... Sometimes you need to say I've had enough of this, let's start over with something new without the inherent and needless complexity. It's only smart to do so.
Well like, you're not wrong I guess
What do you suggest ?
Dude. You might have read my comment in which I said React sucks. Is there a shortage of js frameworks that you're asking for a suggestion?
@@j.r.r.tolkien8724 you said "just use a better tool", I understood that you prefer another framework other than react, if that's the case what do you suggest ?
I told you what I suggest. Another suggestion? Read any book on formal logic or discrete mathematics such as the one by Susanna Epp.