Finally someone talked about the problems with RSC! Thanks a lot!
@sealone77711 ай бұрын
That’s interesting perspective and I feel the same about SSR. It’s incremental improvements. I’m not sure if using nextjs is considered vendor lock as you can deploy anywhere using docker. Didn’t really consider the cost side of things and you are absolutely right.
@dechobarca11 ай бұрын
Hey man, I saw your video on Bun the other day, and now this. Just wanted to say I appreciate your honest thoughts on these topics, instead of just follwing the latest hype. Cheers!
@MattHeslington11 ай бұрын
Same here!
@hrsikeisa11 ай бұрын
bruh yes, Mehul has to run a business and does our portion of due diligence before diving into any of the latest tech hype. For this reason I value Mehul's opinions over many other tech influencer who are riding latest hypes for views. Also I can now actually appreciate that Codamn is not just a course selling platform it's more of a tech company - so many awesome features GPT-4 integrations, Sandboxes, interactive learning (especially the AWS course) ... awesome stuff.
@neociber2411 ай бұрын
If a component needs data from the server anyways, moving the component to the server instead of making a request from the client could make sense. I like this new model because a component can get the data it needs directly instead of passing it down with multiple context but still don't know how much difference it makes to move the computation to the server.
@kalpeshgajare81068 ай бұрын
need to explore this
@sid0611 ай бұрын
Thank you. These videos are invaluable (this one and Prisma).
@shivangrathore11 ай бұрын
rsc is good for making in blogs/articles kind of websites, where crawlers/spiders needs to visit the site.
@neociber2411 ай бұрын
For sure we need more frameworks to use RSC just being Vercel locks you in.
@Hanuman_hun_mai11 ай бұрын
Sir I believe that using RSC in next.js is a really great boost to developer experience , if we develop our projects using React Server Components than we can all together eliminate use of state management libraries (as state management is simpler when you use RSC) and it also simplifies the data fetching patterns, even when creating a full stack app it feels like we are just writing react which we are used to.
@neociber2411 ай бұрын
That's something I don't see people talk enough. With RSC the component can get the data directly instead of loading on the root and pass it down with context. The downside with that is that you need deduping if multiple components need to make the same query to the db
@Gina_DT11 ай бұрын
Subscribed and appreciated
@imkir4n11 ай бұрын
Ahh thats for sharing these infos
@clamentjohn11 ай бұрын
How can we static render a portion of the page and make the rest dynamic? Isn't that SSR? So isn't Codedamb using SSR and using vercel compute to generate the dashboard page?
@neociber2411 ай бұрын
You can send an empty shell (SSR) and them fetch the data from the client. With RSC you don't fetch but do the compute on the server.
@imkir4n11 ай бұрын
so does that mean to use page router?
@siddhantota285711 ай бұрын
but what about seo?
@rakib_bhai7411 ай бұрын
NextJs is modern PHP 😂😂
@justine_chang3911 ай бұрын
totally agree with everything 👍👍
@cripz420311 ай бұрын
Would server side rendering be better comparatively for rendering charts and 3d models?
@janyajoshi11 ай бұрын
I think this is a valid case for SSR
@dinoscheidt11 ай бұрын
3D models are rendered into a canvas element, so it’s pure JS (for simplicity sake) on the client side. There is no HTML to pre render. If you have SVG charts that really take heavy compute to generate, like graph network charts, it could maybe make sense if it needs to be available instantly and can be cached on the server. However, avg phones and computers are multi core power houses compared to the tiny virtual server processes like you’d get with i.e. vercel… so if it is real time… you actually wait longer to get that hyper complicated SVG tree than computing it on the client.
@mohitkumar-jv2bx11 ай бұрын
I think he explained it wrongly. I i think he explained SSR as RSC
@copilotcoder11 ай бұрын
Nope he explained right....SSR is basically the the html getting generated using js on the server and the generated js and the js bundle thrown to client while rsc wont throw the already used js bundle to the client
@mohitkumar-jv2bx11 ай бұрын
@@copilotcoder you are explaining it right. Maybe i missed it. But also the customized part of the page could have been rendered on the server also. There is no reason it needs to be only rendered on client. I think that part confused me a bit.
@neociber2411 ай бұрын
I think the explanation was correct, RSC render the component on the server and recreated on the client.
@baeballeverwizard11 ай бұрын
I wonder what the stupidist thing on the stupidest framework for the stupidest language will be
@rishiraj254811 ай бұрын
🎉
@Pptruenoz11 ай бұрын
waercel
@copilotcoder11 ай бұрын
Just love the fact that u r not a rsc fam boy just because others say its awesome....rsc shit but its hyped....
@blipojones211411 ай бұрын
React is an SPA thing. That it. It wasnt designed to be anything else and the system that has grown around it. Everyone just needs to stay in their lane.
@neociber2411 ай бұрын
That doesn't make sense, you can use React on the server with SSR for a long time.
@blipojones211411 ай бұрын
@neociber24 let me say it a different way. React started off as and was designed SPA library.. It should have stayed JUST and spa library instead of doing any server side stuff. Focusing on server side components was a mistake.
@deadchannel843111 ай бұрын
@@blipojones2114 server side react is pretty nice to use though.