React Server Components launched in 2022 with a lot of promise and a complicated developer experience. Three years later, in mid-2026, they finally feel like a default rather than an opt-in. The combination of Next 16's stable App Router, React 19.2's compiler, and Turbopack production builds shipping has done what no individual release could.
The quiet win is the React Compiler going on by default. Most of the manual `useMemo` and `useCallback` discipline that filled senior engineer time has evaporated. We migrated a 240-component app and removed 1,400 lines of memoisation noise with no measurable regression.
The louder win is the streaming server render model finally being legible to teams. The mental model — server components by default, client components when you need interactivity, suspense boundaries where data lives — clicks for new joiners in a couple of days now. In 2023, it took weeks.
The trap is treating RSC as a free LCP win. It's not. The data-fetching waterfall you avoid on the server can recreate itself on the client if your suspense boundaries are placed wrong. Profile under throttled network. Measure TTFB and INP separately. The compiler doesn't fix the architecture.
If you've been on the App Router for a year, the 16 upgrade is mostly free wins. If you've been deferring it, mid-2026 is the right moment. The ergonomics have caught up to the marketing.
