You don’t need this in React.js

What do you think? Let me know in the comments below
Are you confused where to start coding/what to learn/what roadmap to take? Take this free 2 minute quiz: codedamn.com/c...
👉 Checkout codedamn on social:
✨ Instagram: cdm.sh/ig
✨ Twitter: cdm.sh/twt
If you found the video valuable, please leave a like and subscribe ❤️ It helps the channel grow and helps us push out more valuable content.
✨ Tags ✨w

[@sahilaggarwal2004]

Finally someone talked about the problems with RSC! Thanks a lot!

[@dechobarca]

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!

[@MattHeslington]

Same here!

[@2hari-g2b]

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.

[@sealone777]

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.

[@neociber24]

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.

[@sid06]

Thank you. These videos are invaluable (this one and Prisma).

[@kalpeshgajare8106]

need to explore this

[@shivangrathore]

rsc is good for making in blogs/articles kind of websites, where crawlers/spiders needs to visit the site.

[@Gina_D_Arts_and_Life]

Subscribed and appreciated

[@neociber24]

For sure we need more frameworks to use RSC just being Vercel locks you in.

[@scripting_secrets]

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.

[@neociber24]

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

[@clamentjohn]

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?

[@neociber24]

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.

[@imkir4n]

Ahh thats for sharing these infos

[@rakib_bhai74]

NextJs is modern PHP 😂😂

[@imkir4n]

so does that mean to use page router?

[@siddhantota2857]

but what about seo?

[@justine_chang39]

totally agree with everything 👍👍

[@mohitkumar-jv2bx]

I think he explained it wrongly. I i think he explained SSR as RSC

[@copilotcoder]

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-jv2bx]

@@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.

[@neociber24]

I think the explanation was correct, RSC render the component on the server and recreated on the client.

[@cripz4203]

Would server side rendering be better comparatively for rendering charts and 3d models?

[@janyajoshi]

I think this is a valid case for SSR

[@dinoscheidt]

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.

[@rishiraj2548]

🎉

[@baeballeverwizard]

I wonder what the stupidist thing on the stupidest framework for the stupidest language will be

[@Pptruenoz]

waercel

[@copilotcoder]

Just love the fact that u r not a rsc fam boy just because others say its awesome....rsc shit but its hyped....

[@blipojones2114]

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.

[@neociber24]

That doesn't make sense, you can use React on the server with SSR for a long time.

[@blipojones2114]

@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.

[@deadchannel8431]

@@blipojones2114 server side react is pretty nice to use though.