4 ms·
Vercel just does not get it, it tries to sell SSR-first(and that's what Vercel cares commercially, understood that) to CSR-works-too every time it gets a chance
by synergy20 4y ago
Vercel just does not get it, it tries to sell SSR-first(and that's what Vercel cares commercially, understood that) to CSR-works-too every time it gets a chance. It's not about document at all, if anything the document should never fake SSR-first to something like: set this flag then you get a CSR too, it does not work that way.
It's about the burden of mixing SSR and CSR, Vercel's next.js and sveltekit are both SSR-first by design no matter how you sugarcoat it. I may use them when I need SSR one day, but please stop overselling it as CSR-ready.
Talking about documentation, please do not forget Vuejs, it has the best document all in one place in the JS ecosystem, by the way, it is a true CSR SPA and its SSR(nuxt) is truly an opt-in.
- leerob 4y agoThe core of Next.js is static/CSR. There's a one line configuration option to set your application in this mode—if you don't want to use the server, you don't have to.
- nicoburns 4y agoThe obvious question is: what's the advantage of using Next (over, say Vite) if you're not doing SSR?
- satvikpendem 4y agoIf you ever wanted to migrate to SSR, the path is open with Next, unlike Vite (without a lot of extra configuration).
- crubier 4y agoClean architecture, common patterns, lots of docs, fast compilation, horizontal scalability (one bundle per page), etc.