zhalz

I switched from Next.js/React to Rails for my side projects due to JS ecosystem fatigue. Anecdotally, I've noticed some people making the same move. The open-source finance app Maybe is one that pops up on a lot of searches.

imo Rails has been having a bit of a revival ever since v7 introduced a cleaner approach to front end development with Hotwire (specifically, Turbo and Stimulus) to get SPA-like behavior with relatively little effort. What I love about modern Rails is that it's an evolving framework that is still anchored to a consistent vision for developer productivity. Now with 8.0 having just been released, Rails is increasing built-in support for deploying outside managed providers like AWS.

I can't speak for whether it's going to see a resurgence among big companies other than famous users like Shopify, but I can't see myself using Next over Rails for any of my personal projects, even as someone who writes JavaScript and React code professionally.

Relevant links: - Maybe moves to Rails: https://github.com/maybe-finance/maybe/wiki/Moving-from-Reac... - Rails 7.0 release announcement: https://rubyonrails.org/2021/12/15/Rails-7-fulfilling-a-visi... - Hotwire: https://hotwired.dev/ - Rails World 2024 Keynote w/ DHH, introducing Rails 8: https://www.youtube.com/watch?v=-cEn_83zRFw - Rails 8.0 Beta: No PaaS Required https://rubyonrails.org/2024/9/27/rails-8-beta1-no-paas-requ...

It sounds like the reasonable version of this argument would be "We've been using React with a Rails back end for a while now, and rather than refactor our front end to use Hotwire/Alpine/etc. and be more compatible with the modern Rails paradigm, we'd rather keep our existing front end and move to Next."

Judging from depth of thought in the the actual arguments he's making, I expect that he's deploying to Vercel.

Rails already includes Turbo Native for use cases like this, though: https://turbo.hotwired.dev/handbook/native