Definitely still Rails for me, both for personal projects and for work. There are so many hidden requirements in SaaS products that have been baked into Rails a

Definitely still Rails for me, both for personal projects and for work. There are so many hidden requirements in SaaS products that have been baked into Rails and popular rubygems, getting to build on top of all that work is wonderful. It also makes coming back to a project to update it in a few months/years standard and simple. If you haven't played around with Rails for a bit, things have gotten simpler in the past few years. Doing a quick demo/todo app on Rails 7 is delightful. With hotwire/stimulus, you get frontend performance that feels like React, but you're writing simple HTML/ERB templates and partials and some light JS controllers. It's quite nice. Scaling those apps to lots of complexity is still an interesting challenge, and we're leaning towards React frontends on top of Rails APIs when the frontend is complex, but if you're building a standard CRUD app, Hotwire/Stimulus just lets you motor through the build and spend your time/money on user-facing value.