This comment is highly misleading. It implies that SSR vs CSR is an “either or” proposition: > SSR rendering on the other hand... Requests go back to the serve

This comment is highly misleading. It implies that SSR vs CSR is an “either or” proposition: > SSR rendering on the other hand... Requests go back to the server... Totally ludicrous. For Next.js, this description of routing and rendering is “Totally” incorrect. I don’t know about other SSR frameworks (except maybe PHP, which does actually work as the parent comment describes), but with Next.js, you get SSR on first page load and CSR on subsequent clicks. Thats the whole point of next/router and the <Link> component. Hovering a <Link> will download (“pre-load”) the tiny JS file required to render the next page. Clicking it will trigger client side rendering, without any new server side page load. The complexity that causes this kind of misunderstanding is the best argument against SSR.