Watch this if you hate React Server Components

Astro's approach with server-side/static rendering by default and its islands are and always will be the right approach for this. Next.js and React have become a framework where you have to think too actively about rendering details.

The only unfortunate part of the article is because it is React and somewhat Next focused it didn't uncouple streaming from Server Components. It is unfortunate because I think streaming is where most of the benefits here comes from. Server Components might even be a detriment, but there is no comparison to verify either way.

Nadia is the bomb. I love her book Advanced React!

For SPA's, If the backend is aware of the frontend routes, you could: - Send the html to client, not close connection, stream in the the data need for the page. (i.e. while the js loads, you already have the data so no waterfall for that - Easier: add prefetch headers for all resources needed for that page (assuming backend know front-end routes and which data is needed). When the request runs in the frontend loaders, it immediately resolve and data is instant visible Which from my perspective seems way less complex that rendering the page, with all quirks and potential hydration issues.

Can someone tl;dr? Is SSR faster? I don't want to watch 40 minutes of technicalities

I think I understood about 75% of this already but really interesting dive. Thanks!

QUICK IMPORTANT CLARIFICATION: at 36:00, I went looking for the tailwind flag, but this is a NextJS feature (W next) which lets you inlineCSS which is still experimental so please use with caution! Thank you for your time :D

Bro your facial expressions in thumbnails are insane :D

Cool breakdown Theo!

6:04 I'm really confused, can you please help me understand this? Everything else I'm reading says the opposite of this, RSCs only run on the server (component code is not sent down) and server components run on the server and client (component code *is* sent down).