I Was Wrong About React Server Components...

I've been thinking a lot about RSCs and it turns out I was kind of wrong about them...

S/O Flip Media for the awesome edit 🙏

[zaabimahdi]

When considering the security concerns and Single-Responsibility Principle (SRP) of web applications, it is worth noting that the Single-Page Application (SPA) concept was originally introduced to decouple the frontend and backend. However, there is a trend towards introducing 'colocation' in modern web application architectures(NEXT, React server component..), which brings the frontend and backend closer together and resembles the traditional Model-View-Controller (MVC) architecture. This shift towards colocation may have implications for both the SRP and security of web applications, and developers should carefully evaluate the trade-offs involved
As a result, If a hacker gains access to the server where a frontend application is deployed, they could potentially compromise both the frontend and backend of the application.

[Victor-jzxu]

Honestly, just for the fact that i do not have to "context switch" as much when using RSCs is enough of a sell

[danmuller]

I don't have a strong opinion on this whole server components thing. What I do have a strong opinion on is that we shouldn't be afraid to make mistakes and admit them later and I just wanted to thank you for doing exactly that!

[guyincognito]

JS in your HTML, CSS styles inline in your HTML, SQL queries comingled with markup, backend code right there next to your front-end code... You fancy new hipster web devs are re-discovering all the "great things" we had 20+ years ago. What will you come up with next? Using tables for layout?!

[MNbenMN]

The more things keep evolving with modern web dev lately, the more it feels like old school. Server stuff (data persistence and processing) in one place generating client stuff to deliver a UI that calls back home. I'm all for it. Having everything rendering on both ends always felt like too many gears turning. Moving on from double rendering everything seems like a good direction.

[mehulsharmamat]

Still waiting for backend CSS. wake me up when that happens

[SeattleSpursFan]

I will be honest, I did NOT miss this and have been waiting for an influencer like yourself to grasp and get excited about it. Now, I'm looking forward to seeing it's effect on the evolution of the T3 stack.

[danielismyhandle]

With the server$ maybe we can make the variables prefixed with $ so we know what belongs to the backend ? Oh wait...

[knsense]

I once heard the phrase "Technology is like a pendulum, moving forward and backward". I think we've gone full circle, RoR, Django, Laravel, etc. Have been doing this for YEARS, I can see how in a couple of years we will be going back to CSR

[BosonCollider]

This is where Fresh and Astro are less confusing with the island model imho. If its not explicitly declared as an island, it runs on the server/edge.

[moitp]

Cool, we are reinventing PHP.

(Oh, and improving DX doesn't justify everything, DX can have very bad impact on knowing how things really works and performance alone just to talk about that small aspect)

[ChrisVisserDev]

What I love most about your channel is your honesty towards your understanding of things. It happens a lot when we think we get it, but it turns out that we didn't after all. All developers are going trough this, even the most experienced ones, but you are one of the few that actually is open and clear about it!

Keep up with this great content!

[red]

React server components is the re-invention of PHP, we've gone full circle.

You're welcome, fastest analogy and cheapest way to wrap your head around em.

[nan]

Something feels off when we have to spend weeks talking about the mental modal of something upcoming when it's basically just what we had 15 years ago.

[marlonjerezisla]

One step closer to PHP from the 90s! 👍

[magne]

4:24 The massive confusion surrounding RSC’s all across the board is a major red flag; if the experts are confused, imagine how confused all the novices will be. Developers need to think fast about these things, and that begins with a clear conceptual model supported by clear distinctions: different things that look different, or kept separate in other ways. RSC’s are not there yet.

[MrMudbill]

I started learning web dev with the LAMP stack, and lately it feels like we're getting closer and closer to it, after leaving it out in the rain for years.

[Ruhigengeist]

Nah. The best part of the PHP world is that you don't need to restart a service to see your code changes take effect, you just refresh the browser. The iteration cycle for backend is much faster that way. And with opcache, performance is very very good. You can go even further and run PHP as an event loop to get even more performance if necessary.

[statt]

Much of RSC seem to assume that the API (of which there may be multiple) is solely consumed by the front end, but for many dashboard SaaS projects I work on these APIs have use cases beyond the front end, data being ingested through other event sources. Mingling react code with these APIs seems like a non-starter there

[nbb]

As much as I enjoy React and Next, I'm sceptical of React 18. It took a few too many years to release it and I see too many React-based frameworks and libraries have long-standing open issues for React 18 adoption. As much as I appreciate the new React concepts and the new Next Router, the ergonomics around it are not great, the complexity is too high, and the caveats are too many. Considering new alternative architectures such as resumability in Quik, I increasingly doubt the future of React.