I'd still choose Python/Django as the basis for a startup now. Would probably choose Ruby/Rails if that was where my expertise lied, although I still see lots of Python engineers (in London) and few Ruby engineers.
I think the pattern of a monolith that's very easy to rapidly develop on, plus specialist services around the edge that might be high performance/security/etc and are written in languages like Rust is a pretty good strategy. Personally, having seen the speed of development on a Django project, it's hard to justify much else for the boring CRUD core of a service.
This looks like a web service framework, rather than a web application framework like Rails/Django. Like it's closer to Sinatra/Express than Rails -
The speed of Rails comes with rapid development & strong conventions leaving the important stuff (like business logic and building something) to you.
Once you get to a size where scale is an issue with Rails, you'll have a startup that's working - it's a better problem to have than a startup that has perfect fast code but no customers.
They never implied "en masse." But yes, for what it's worth, those that would use Rails 10 years ago are now increasingly using JS based frameworks, such as NodeJS with express and/or Next.js. In fact, many people who are in web dev these days only know JS/TypeScript, they know zero Ruby at all.
Or maybe: those people that were using Rails 10 years ago are still using Rails now and those people that entered the job market in the last 10 years are using JS frameworks. That would match more closely what I see.
Exactly, that's what I meant, I should've worded it better. I see no reason for most companies who are successful to move off of Rails, but then again, many big ones have over the years [0], including Twitch, Airbnb, Hulu, Coinbase, SoundCloud, and even Twitter.
The point I'm making is that people leaving for nim is a HN thing to say that's unrepresentative of what's actually happening in the rest of the world.
Wondering what folks are up to.