Paul Keen<p>Hardcover team ditched Next.js for Rails+Inertia.js and got faster pages, better SEO, and lower costs. Sometimes moving back is moving forward.</p><p><a href="https://ruby.social/tags/Rails" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Rails</span></a> <a href="https://ruby.social/tags/Inertiajs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Inertiajs</span></a> <a href="https://ruby.social/tags/webdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>webdev</span></a> <a href="https://hardcover.app/blog/part-1-how-we-fell-out-of-love-with-next-js-and-back-in-love-with-ruby-on-rails-inertia-js" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hardcover.app/blog/part-1-how-</span><span class="invisible">we-fell-out-of-love-with-next-js-and-back-in-love-with-ruby-on-rails-inertia-js</span></a></p>