When do statically rendered pages instead of dynamic RSC with server-side fetching make sense?
Unanswered
Japanese Bobtail posted this in #help-forum
Japanese BobtailOP
The great theme of latest Next.js app router with RSC is that server-side fetching is preferable and typically faster on many metrics for the end user, instead of the waterfall of network requests that happen in a SPA-style static page.
But aren't there some use-cases where a static page is much better? For example a
But aren't there some use-cases where a static page is much better? For example a
/conversations/[conversationId]/page.tsx route, for viewing DM conversations. If it's a static page, navigating to different DMs could happen instantaneously with skeletons shown in the DM UI while a request to the app API is made for the conversation contents.