Next.js: Pages Router (legacy) — компромиссы и trade-offs

Question

Accepted Answer

Pages — simpler mental model, whole page hydrates; don't migrate working app without RSC reason.

## Разбор

- **Simplicity и stability.** Smaller model: one component per page, one data function, classic hydration. No streaming, no boundaries. CRUD и content sites — adequate, battle-tested.
- **Cost — bundle size и rigidity.** Whole page hydrates — *all* page component JS ships. No per-component server/client split, partial hydration, independent slow section streaming.
- **Когда НЕ migrate:** working Pages app не rewrite «because newer». Migrate когда нужны RSC — smaller bundles, streaming, server data in components. Routers coexist — incremental migration.

## Итог

Pages still valid; migrate for specific RSC benefits, not hype.