<p>This is the first post of my blog that I wrote after migrating from gatsby to Next.js.</p>
<p>Although I really like gatsby, I still find it difficult to use it and hard to set up in particular to support my needs.</p>
<p>After several years and when I decided to write a couple of o blog posts my the build time of the site was slow because as you might know the pages on gatsby are generated on build time.</p>
<p>But let's not focus on that because I'm still a big fan of gatsby for single-page websites that stay static and don't need to be rebuilt often.</p>
<h2>Why Next.js then?</h2>
<p>I'm a full-stack developer that has been working with node.js and react for a long time and that was one of the reasons I decided to migrate to Next.js, it's a framework that is easy to use and supports backend operation particularly using lambda functions and webpack 5 support out of the box with easy configuration.</p>
<p>Also, a big plus as a typescript passionate developer is that Next.js supports typescript out of the box and provides amazing tooling to work with it.</p>
<h2>Small things</h2>
<p>The small details might not be that important to you but I think it's worth mentioning.</p>
<ul>
<li>SSR (Server Side Rendering):</li>
<li>SEO (Search Engine Optimization):</li>
<li>Code splitting</li>
<li>Page caching</li>
<li>Pagination</li>
</ul>
<p>Finally, the framework is fast and easy to use and I'm sure that it will be a great choice for a developer that wants to start a new project.</p>


Blog.

Why did I choose Next.js?

Why Next.js then?

Small things