Gatsby vs Next

I actually disagree with a fair amount of finer points on this, but it's a good overview of the differences https://dev.to/alex_barashkov/comparing-gatsby-and-nextjs-for-website-development-13b7
DEV Community
Comparing Gatsby and Next.js for website development
Gatsby and Next.js, from a first glance, could look pretty much the same. Both are React-based...
V
vcarl779d ago
for example,
Next.js does not have a plugins ecosystem, so for fetching data from a CMS, we have to find SDK, learn an API, think about the reusability of that integration within the website on different pages, probably make some SDK wrappers for common use cases, or HOC. Maybe it’s ok for small sites, but for large ones it will require spending some time thinking about the overall data fetching architecture and scalability of the solution.
I ran into a TON of problems with Gatsby plug-ins when building a large site. it worked well for small uses cases, but once I wanted to do somethi g specific that wasn't exposed by the existing plug-ins, the plugin-centric design just added more layers to sift through and debug and oof this was in no way my experience
Both frameworks can handle it by using additional libraries. Gatsby handles it with a plugin and minimal configuration.
I had to do a ton of custom logic to get a Gatsby sitemap where we wanted it for seo, tho I guess that was Gatsby v2. not sure how it's improved since
V
vcarl779d ago
this is a pretty solid deep dive too, also includes remix https://satellytes.com/blog/getting-started-gatsby-next-remix/
Getting Started: Gatsby vs. Next.js vs. Remix | Satellytes
Getting Started: Gatsby vs. Next.js vs. Remix | Satellytes
We developed a simple blog application in Gatsby, Next.js and Remix. Learn about the differences in the development process and the technical concepts behind these three frameworks.