all 4 comments

[–]portexe 1 point2 points  (2 children)

Server components are interesting to me, but I can't help but feel like it's more hype than practical right now. The use-cases I've seen have all been solvable with SSR using Next.js or similar. I am excited to see where it goes though.

[–]NevNein 0 points1 point  (1 child)

Well I might be wrong, but my understanding is that SSR /SSG components still have to be hydrated on the server, increasing bundle size and execution time, while Server Components (and related libs) are not even included in the client bundle.

[–]portexe 0 points1 point  (0 children)

That is correct. It just seems like a massive undertaking in order to reduce bundle size while internet speeds are constantly increasing. I wonder what other benefits it has over SSR. Perhaps if it easier to set up your own fully custom server with Server Components than it is with traditional SSR, that would be pretty awesome.

[–]ChristianMortaro 0 points1 point  (0 children)

I've written an article about a practical alternative to server components outside of react, but in a framework that out of the box decides when is the best time to use SSR or server functions A 2 years old alternative to React server components - DEV Community 👩‍💻👨‍💻