3 ms·
I agree with this weird mismatch of overcomplexity for the problem it's trying to solve. I did really like though the Gatsby model of ingesting all your source
by madeofpalk 6y ago
I agree with this weird mismatch of overcomplexity for the problem it's trying to solve. I did really like though the Gatsby model of ingesting all your source data into GraphQL and then having a standardised way to query and build pages from this. I wish Next.js would learn something from this.
I was using Next.js to build a staticly-generated website (so within the remit of Gatsby) but eventually i outgrew the limitations of static site generation (23k pages and counting...) it was so easy to switch to a traditional server-generated model with Next.js. I'm incredibly greatful for picking up and sticking with Next.js for this.
- tootie 6y agoI think for any commercial site, it's likely cheaper to use a platform like next or nuxt and a CDN rather than choking your build pipeline with static generation. You still get static performance and just offload it to an edge network and CDN costs are racing downwards.
- thesandlord 6y agoNo need to do static generation at build time or fully server-side rendering with Next.js either, you can build static pages at runtime with ISR https://nextjs.org/blog/next-9-5#stable-incremental-static-regeneration https://nextjs.org/blog/next-9-5#stable-incremental-static-r... (edit: whoops this was for the parent comment)
- madeofpalk 6y ago"incremental static rendering" is... server-side rendering, at least that's what I meant. Rendering pages on demand for users as they request them, with (optional) invalidation to render it again later.
- duhi88 6y agoThat feels like the React community in a nutshell.
- madeofpalk 6y agoSeems like any developer who isn't able to think critically about the decisions they make.