Nothing is blown away in terms of client state persisting, but revalidateTag/revalidatePath re-renders entire RSC tree from the root including layouts (and refetches everything in them). Ideally, there should be a way to revalidate the page segment separately (similar to navigation)

React started componentization of web dev
React Server Components continues it

One thing that I noticed is that people just habitually default to Tanstack Query for data fetching when using React. And in this case, RSC sorta stays in the way instead of helping.

On which Tanner pointed out (rightly so, imo) that you still need selective revalidation from the client.

"Vercel AI SDK - how do I get ai to interpret the tools response?"

👇

Caching Prisma queries with dynamicIO in Next.js

Composable caching in Next.js with dynamicIO