2 ms·
Too subjective. If server cost is not a problem for the thing you call "multi-page", it is not a problem for server-side rendering either. Vercel didn't invent
by fatih-erikli 4y ago
Too subjective. If server cost is not a problem for the thing you call "multi-page", it is not a problem for server-side rendering either.
Vercel didn't invent server side rendering. It was always there.
- aobdev 4y agoUnfortunately the given examples (Next and Nuxt) are much slower than traditional template engines, even in "slow" languages like Python + Jinja2. This may not translate into financial cost at the scale of your average startup but it does have a measurable performance cost for each page load.
- fatih-erikli 4y agoYou don't need next or nuxt. Server side rendering supported by React itself. You just need a node-js running instance.
- chrismorgan 4y ago> It was always there. This article isn’t talking about server-side rendering, as one might have used the term 10–15 years ago (but not really before that, because it didn’t need a name before that, because client-side rendering wasn’t really a thing), but rather Server-Side Rendering, which is when you use client-side rendering tech, but run it on the server side (typically “as well”, but not quite necessarily).