React Server Components face DX backlash

RSC still looks stronger on architecture diagrams than in day-to-day developer workflows. When even React’s own docs warn framework authors to pin versions because the underlying bundler APIs are unstable, the “just works” story is clearly not finished.

• –Evan You’s critique lands because it is not anti-server by default; he explicitly says RSC unlocks useful patterns, but the tradeoffs and mental overhead have outweighed the promised DX gains
• –The sharpest complaint is not raw performance but scope creep: RSC pushes React deeper into bundling, routing, server runtime, and build tooling decisions that used to be framework-agnostic
• –The gap between React’s official docs and real-world implementations remains a core issue, especially for teams outside the tightly coupled React-plus-Next path
• –This makes RSC feel less like a universal React primitive and more like a framework architecture bet that still carries significant operational cost for ordinary app teams