Comment by ironmagma
3 years ago
SSR support is only needed for public-facing websites that will undergo some kind of search engine indexation. For most apps this is not necessary since most apps are not accessible publicly.
3 years ago
SSR support is only needed for public-facing websites that will undergo some kind of search engine indexation. For most apps this is not necessary since most apps are not accessible publicly.
NextJS does more than SSR, like determining routing based on directories and making React Server Components and Actions so simple it's hard to not choose NextJS
They've removed a ton of pain from full stack React/JS/TS
OK, but on the other hand I've heard from someone who worked at a startup that unnecessarily chose NextJS despite no requirement, and it really held back the organization for the rest of its existence, limiting velocity. Simple things like fetching queries become harder due to the split lifecycle. Relevant HN thread: https://news.ycombinator.com/item?id=36472166
Yeah, you definitely buy into a paradigm and ecosystem that has its own flaws. It's all tradeoffs and right for for sure.
My new project requirements for well with NextJS. I was mainly pointing out that there are a number of benefits for the drawbacks.
[dead]