RSC introduces client confusion, development complexity, and latency concerns

Loading large prompt templates, validation schemas (like Zod), or establishing SSL connections to an external Vector Database (e.g., Pinecone or Weaviate) introduces significant latency during initialization.

Next is recommended first in the React docs, and the Next App Router is also mentioned as the main example under 'Which features make up the React team's full-stack architecture vision?' Next is still the only production implementation of RSCs. The added complexity can also be a trap that leads to confusion, such as accidentally using Context or hooks in Server Components (which throws errors).

client confusion with RSC, slower development due to the complexity. Real challenges of the NexJS over engineering, app router, middleware, edge, functions, etc. Simple apps feel too complex, steep learning curve, performance concerns, cold starts on serverless, RSC introducing latency