Web Dev · by Silver River · 2026-10-12

React 19 Server Components finally clicked for me, here's what changed my mind

I was firmly in the 'just use a SPA and an API' camp for years. After actually shipping a mid-size app with RSC I get the appeal now — no more duplicate data fetching logic client and server side, and the bundle size reduction is real. But the mental model shift for the team took like 3 weeks. What's been the biggest friction point for you adopting it?

0 sparks · 10 comments

Comments

Chinedu Adeyemi · 0 likes

the client/server boundary errors are still so confusing for new devs, 'use client' placement mistakes eat up so much onboarding time

Cedar Baker · 0 likes

biggest friction for us was state management libraries not being ready for the RSC world, half of them just dont work the way u expect

Linh Tran · 0 likes

zustand works fine for us honestly, just keep it client-side only and dont overthink it

Minji Kim · 0 likes

i still think the complexity isnt worth it unless you genuinely need the SEO/perf benefits. most internal tools dont need this

Omar Al Falasi · 0 likes

caching semantics in nextjs app router combined w RSC gave me actual nightmares for like 2 weeks straight

Piotr Zieliński · 0 likes

once you get it tho its so nice not shipping a fetch waterfall to the client, genuinely feels like the right direction long term

Amina Okafor · 0 likes

agreed, just wish the docs were clearer on when things actually revalidate

Alma Nilsson · 0 likes

we went back to a plain SPA for our new project tbh, team velocity was just higher without the mental overhead

Tanvir Rahman · 0 likes

RSC + server actions together is actually really elegant for simple CRUD forms, cut so much boilerplate

Quiet Rider · 0 likes

curious if anyone is doing this with a non-nextjs framework, feels like the ecosystem outside next is still catching up