Your long form videos are awesome. They allow to really understand how React works and what RSC brings to the table. I couldn't help smiling when you said functions are not serializable. As I know you're also into Qwik and that the Qwik team managed to make functions serializable, it's funny to see that you're able to stay in the context of each lib / framework. If you could explain how they did that (making functions serializable) it could become another great video of yours. Even a great collab with a member of the Qwik team. Time for me to watch your 'deconstructing React' video ;)
This video is underrated. You should make mini powerful shorts by splitting this so its a little more digestible. I bet you 8/10 next devs have no clue what they are doing
Amazing video my friend. I’m so happy that you made this video. You’re very talented at explaining these things. It’s apparent that you know what you’re talking about.
Seeing how to implement RSCs yourself is incredibly educational. Would love to see more of these in-depth hands-on videos on concepts like Server Actions, Suspense, Caching/Revalidating etc. Thank you for this!
Thank you @Tejas for your contribution to RSC's. I've been working on RSC's for quite a time now and wanted to explore how they work internally so, this helped me a lot.
Really liked the video, it is great that you break down concepts. I may not understand everything, but fundamentally understood a lot of things. Thanks for making this video, keep coming up with good stuff.
Gold content Tejas please bring more of these as we don't get it anywhere else. Also I would be great if you can share how you learn about all this building things from scratch
@@tejask makes sense ill follow dan’s work closely and try to learn more of these. Also giving talk similar to what you showed about building ssr and file based routing at a local meetup of react Pune really excited to show people how these things work. Thanks for all the effort bringing these content.
You're skills on deconstructing these nuanced complex topics are so brilliant! Keep it up sir! What would you suggest a dev could do to gain in-depth knowledge of these new patterns and React/frontend in general? Thanks :)
LMAO, this basically renders part of my React India proposal pointless. I could just link them to this video and they'll get similar (probably better) value. Another good one, Tejas!
This has been truly useful! Everyone talks about meta frameworks and server components togather, so it's hard to understand the core principles in isolation. Your video helped me greatly with that. I wonder though if all server components need to be hydrated 🤔. I guess there's nothing stopping us from writing some application/meta-framework logic that mounts multiple react roots inside a given html output from the server. That's probably how ASTRO islands work, right?
How would this look like if we introduced a client component? Lets say we have a single button component with an onClick prop. How does the serialization proceed with that? Is there a placeholder for it or something similar? Essentially that serialized object will be parsed by the server to generate html and html for the button will be there. So I am wondering how serialization looks like when we mix client/server components
RSC (React Server Components) is a solution looking for a problem. I wish the Next.js people would just fork the project and "fork off", let React be useful the way it already is as a View / Frontend / Client library. /end of rant.
React is a framework, not a library. If react is a library, then why do I think to structure my entire repo around it? d3 is a library. I don’t have to structure my repo around it. I can use its functions and objects where I need, regardless of what framework I’m using. React is not a library. This is such a weird propaganda that react pushes for some reason.
Your long form videos are awesome. They allow to really understand how React works and what RSC brings to the table.
I couldn't help smiling when you said functions are not serializable. As I know you're also into Qwik and that the Qwik team managed to make functions serializable, it's funny to see that you're able to stay in the context of each lib / framework. If you could explain how they did that (making functions serializable) it could become another great video of yours. Even a great collab with a member of the Qwik team.
Time for me to watch your 'deconstructing React' video ;)
Hey thank you so much for this thoughtful comment!!
This video is underrated. You should make mini powerful shorts by splitting this so its a little more digestible. I bet you 8/10 next devs have no clue what they are doing
Amazing video my friend. I’m so happy that you made this video. You’re very talented at explaining these things. It’s apparent that you know what you’re talking about.
I appreciate that!
Seeing how to implement RSCs yourself is incredibly educational. Would love to see more of these in-depth hands-on videos on concepts like Server Actions, Suspense, Caching/Revalidating etc. Thank you for this!
My pleasure
Thank you @Tejas for your contribution to RSC's. I've been working on RSC's for quite a time now and wanted to explore how they work internally so, this helped me a lot.
You're most welcome
Really liked the video, it is great that you break down concepts. I may not understand everything, but fundamentally understood a lot of things. Thanks for making this video, keep coming up with good stuff.
Thank you so much! Happy to clarify anything you didn’t understand!!
Gold content Tejas please bring more of these as we don't get it anywhere else. Also I would be great if you can share how you learn about all this building things from scratch
Hey thanks! In this case, I just read Dan’s post.
@@tejask makes sense ill follow dan’s work closely and try to learn more of these. Also giving talk similar to what you showed about building ssr and file based routing at a local meetup of react Pune really excited to show people how these things work. Thanks for all the effort bringing these content.
I share it on my Likedin, I found out this is one of the greatest explanation about this topic.
Deeeeeep knowledge. Thanks for making these videos and diving deep into the React core.
GOLD MINE of a youtube channel
@@dumbfailurekms love it, please share
You are awesome Tejas. Please don’t change always teach like you do. Love you bro ❤
Thanks! great content, learned a lot.
Thank you as well for your support!!
You're skills on deconstructing these nuanced complex topics are so brilliant! Keep it up sir!
What would you suggest a dev could do to gain in-depth knowledge of these new patterns and React/frontend in general?
Thanks :)
Subscribe to the channel and ask me to clarify things?
I would love to know how nextjs and these metaframeworks do their cache system
bro, please make a web dev course with all the knowledge and industry experience u have , We will buy 🔥
You are a great teacher and fluent
Thanks
Great job Tejas , awesome video ... tks a lot !! I was listening to your podcast ep about zod and trpc ... you are a really rockstar 🎉
Thank you!
Great Video Tejas, I love your approach on this.
Hey thanks a lot!!
Very good video, as always. Learned a lot with it. Thanks a lot for all this great learning content!
Thank you so much!!!
LMAO, this basically renders part of my React India proposal pointless. I could just link them to this video and they'll get similar (probably better) value. Another good one, Tejas!
Still do the talk!!!!!
I was just here telling people how the 1mg team is the best.
@@tejask I still need to show you what we’re working on. Only if I manage to incorporate RSC into it by React India
@@tejask Also you’re just too generous man.
Legend, great speach in Zadar, hope to see you next year too! :)
what terminal are you using? I loved the idea to have the tabs in the sidebar. Btw great video, new sub (y)
High quality stuff !! 🔥🔥
Thanks!!
This has been truly useful! Everyone talks about meta frameworks and server components togather, so it's hard to understand the core principles in isolation. Your video helped me greatly with that.
I wonder though if all server components need to be hydrated 🤔. I guess there's nothing stopping us from writing some application/meta-framework logic that mounts multiple react roots inside a given html output from the server. That's probably how ASTRO islands work, right?
Nice video. Learnt a bunch. 🙏Thanks. But how do you test a react server component?
How would this look like if we introduced a client component? Lets say we have a single button component with an onClick prop. How does the serialization proceed with that? Is there a placeholder for it or something similar?
Essentially that serialized object will be parsed by the server to generate html and html for the button will be there. So I am wondering how serialization looks like when we mix client/server components
Great video, thank you! I have a question, how can two child components communicate with each other as leaf nodes of a server component?
Great video, Tejas! Thanks!
is it production ready now ? as with next 13.4 app router is stable and RSC are default with app router ?
It is nit
Not
Thank you Tejas for another Gem
Happy to serve you!!
React is a framework, mate. It controls the flow of your program, following 'The Hollywood Principle.
Great explanation. Thanks for doing this.
My pleasure!!
Thank you Tejas 🙏🚀
Thank you!
RSC (React Server Components) is a solution looking for a problem. I wish the Next.js people would just fork the project and "fork off", let React be useful the way it already is as a View / Frontend / Client library. /end of rant.
You are a hero :)
Keep it up sirrrr 😊
love this guy
Amazing!!! you are the best!
Can we please get more react stuff please.
16:22
React is a framework, not a library. If react is a library, then why do I think to structure my entire repo around it?
d3 is a library. I don’t have to structure my repo around it. I can use its functions and objects where I need, regardless of what framework I’m using. React is not a library. This is such a weird propaganda that react pushes for some reason.