DEV Community

Discussion on: Next.js - Your next go to framework

Collapse
larsejaas profile image
Lars Ejaas • Edited

I am currently trying to learn Next.js after some projects in Gatsby.js. While Next. js certainly is nice, it IS harder to work with some things than Gatsby.js. Plugins are just harder to implement, because you have to do more things manually + Gatsby. js has a large amount of premade plugins by the community. While GraphQL is super nice I feel that Gatsby rely too heavily on it to some extent. And this part is certainly better in Next. But something like getting the styled components library up and running in a Next application is surprisingly difficult.

Collapse
goldfinger profile image
Caleb

Next has a premade template for styled components you can run when instead of the normal create-next-app, works great. Same as CNA but with the _document created and ready to go.

Collapse
larsejaas profile image
Lars Ejaas

Thanks Caleb. I got thinks working. It's not that things are impossible complicated in Next.js but for someone not super comfortable with Jamstack I would say that Gatsby.js is easier to get up and running. The downside of Gatsby. js is that you tend to rely on all these small plugins made by the community, and when something brakes you have to wait for someone else to fix the bugs...

Thread Thread
gurshehzadsingh profile image
Gurshehzad Singh Author

After all, the process here in React works for providing a better efficiency in usage of third party libraries. And Gatsby or Next.js both are working well as a top layer for React. It depends on what you get first introduced with. The community support works out for both

Thread Thread
larsejaas profile image
Lars Ejaas

Yeah, sure! We are comparing two great libraries, and they are both great! You can do things in next that are difficult to pull off in Gatsby. But generally I still feel Gatsby is easier to get started with. I actually work in next.js on a project right now, but will sure be back in Gatsby again 😊