> Next one finds oneself rebuilding things, that a normal web browser has had at the ready for decades, only because the whole website was forced into a web app

> Next one finds oneself rebuilding things, that a normal web browser has had at the ready for decades, only because the whole website was forced into a web app approach and there is a separate router and all that stuff. At that point using a traditional web framework that simply renders HTML on the server would have been a better choice, but of course it is not hyped like NextJS is. It is not fashionable! Your arguments are not related to Next or server-side-rendering frameworks at all, you arguments are related to static websites vs SPAs (client or server rendered). Although you have some valid points it has been proven that devs rather just use the more powerful approach even if they don't need to. The two ways of building apps (static vs SPA) are just too different and there is more job market for SPAs so even things that don't need to be SPAs end up as SPAs. On top of the FOMO of maybe you might need some dynamism in your pages in the future, it just makes sense to go as SPA from the start.