Like a lot of developers, I like to use my blog as a personal playground to try out the latest technologies. My blog was written in Gatsby, but recently I migrated it to Next.js. In this post, I’m going to talk about my experience, what went well, and what didn’t.
Keep in mind that, while Gatsby and Next.js do have an overlap in functionality, these two tools are vastly different in their feature set, problems they solve, and their philosophy. If you’re interested in a comprehensive comparison between these two frameworks, I suggest reading Next.js vs. GatsbyJS: A developer’s perspective.
Note that since that post was published, both tools have received lots of great updates, especially Next.js, so be sure to check out Gatbsy’s changelog and Next.js blog.
The reason why I started using Gatsby in the first place was because of the way I wanted to author my code and the design I wanted to achieve required more control over the build process.