There is no such thing as "nextjs server components". Next.js has implemented React Server Components. Remix will also implement them once React 19 comes out.
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 😁
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!
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!
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.
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?
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 ?
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
Excellent video. The clear title, helpful diagrams and explanation makes the subject very clear. Wish more tech videos were like this.
I feel like somehow remix has implemented its own version of server components that is slightly more lean compared to nextjs.
There is no such thing as "nextjs server components". Next.js has implemented React Server Components. Remix will also implement them once React 19 comes out.
Yes, doing the same as what React 19 provides with React Server Components and Server Actions.
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.
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 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.
Great video, you are gifted on explaining things
Thank you for talking about this topic ❤
The way you explain the remix I wish I found same tutorial on Nextjs wow 🤯
We need more videos like these!!!
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 😁
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!
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!
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.
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?
nice content bro subscribed! I HATE REDUX, TANSTACK make more vid like this brotha
Useful video, 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?
Yes, all loaders are revalidated and you can import a specific loader in few other routes to consume the same data at different place
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
Thanks, Great explanation.
We still need client state for many other things, we still need Context API to pass this through components
Remix is just underrated ❤
I have a tattoo of it, it's that serious
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 ?
It's NOT React VS Remix. It's Remix VS Next.js. You're missing the point completely!
Vs Astro
Nice explanation
why is it better than using react lazy components ?
so if I have paginated data does remix will revalidate all the pages ?
Do remix vs next js next
So remix is running on the server and serving the API? I don't get it :( I want to write my API in Go or Python...
Keep learning! You can definitely write your API wherever you want and consuming it in Remix, or Svelte or Solid etc...
Hi great video. Can you provide the colorful remix logo to download. Thanks.
Remix is amazing
I love you
Remix js is faster than next js. my personal experience
Library number 109,877 that fixes react state 🤘
Why are you still using react query with redux instead of libraries like jotai and zustand
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
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
If you are comparing Remix with React by writing that Remix is way slower than React, it means you have no idea what you are writing about.
@@coder_one your comment makes me think you've never worked with react before and create the same project on remix
Why was it slow?