> Realistically, most applications will never need to scale up. So what's wrong with a nice framework that allows people to just get stuff done? I've coded wit

> Realistically, most applications will never need to scale up. So what's wrong with a nice framework that allows people to just get stuff done? I've coded with Rails since Rails 3. There are a few issues with rails: 1/ DHH never gets JS right. CoffeeScript, Asset pipeline, and now the new Turbo. Migrating your FE every 3-5 years to a new language stack is the opposite of "get stuff done" 2/ Rails is built for b2b apps (Basecamp). If your business looks like basecamp, then the conventions will work for you, but if it doesn't (think b2c apps), it won't. Examples: ActiveStorage was a mess with no CDN support (it is better now though), Action Cable only supports a handful of connections compared to nodejs. 3/ No ML support. If you want a framework that "allows people to just get stuff done" then use Django. It is similar to rails and has all the bells and whistles of the ML community.