17 ms·
There used to be a time when Next.js focused on server-side rendering of dynamic React apps, and Gatsby focused on generating React-based static sites. Now that
by azangru 7y ago
There used to be a time when Next.js focused on server-side rendering of dynamic React apps, and Gatsby focused on generating React-based static sites. Now that Next has forayed into the static-site generators world, I wonder whether it is about to displace Gatsby.
- vosper 7y agoI think Next is in the sweet spot by making things static when it can, and server-rendered when needed. It's been a real pleasure for me to work with so far (though, prior to version 9 I found it not quite flexible enough, especially wrt routing). I think Gatsby's GraphQL-first approach and emphasis on plugins makes the learning curve a lot higher than it is for Next. I have transitioned my personal projects from Gatsby to Next. Frameworks like these need to balance the ease of getting started with giving users confidence that they're not going to end up in a jail where they can't get the functionality they need. The Next team have walked this line pretty well, and I hope they continue to focus on keeping things simple, but flexible enough for most use cases.