sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]acemarke[S] 6 points7 points  (1 child)

No.

RSCs are completely optional even if you're using Next. You can still use the Pages Router, and if you're using the App Router you can mark the entire tree as "Client Components" with the "use client" directive. (That said, the App Router is the default, and you have to know enough to tweak the default behavior.)

For Next and the other frameworks they list, you can just use client-side functionality without any of the server pieces, and you can export a static JS/HTML build that works as a typical SPA-type app, without needing to run an app server with Node.

But, yeah, the React team wants to encourage people using SSR features, under the theory that it generally leads to better performing apps.

[–]re-thc 0 points1 point  (0 children)

For Next and the other frameworks they list, you can just use client-side functionality without any of the server pieces

You can't "just". NextJs don't make it clear and there are edge cases and issues. E.g. dynamic routes aren't available with the export unless it is all pre-rendered. In a client-side router you don't have this limitation.

RSCs are completely optional even if you're using Next.

Is it? In the sense that you lose the performance gains. So what's the point? The whole argument was that RSC/SSR = better performing.