Yeah, right. Because all the interesting things nowadays happen on the same server that renders your html and nobody calls into other SaaS APIs or interacts with external systems much.
Rails is great for a world where an app was running on one server, but that world just isn't there anymore as much as it used to.
> Rails is great for a world where an app was running on one server, but that world just isn't there anymore as much as it used to.
No, that’s still a choice you can make. It’s still possible to make your app run on one server with Rails/Django/PHP and to scale it horizontally and vertically very easily. The requirements of a web app / web site barely changed in 10-15 years, the only things that changed is that new ways to do the same things appeared regularly : some were real improvements, most are just hype-driven.
If you need to call external APIs you can still do it on the client if that’s what you want or on the server with task queues / messages queues which are still a good practice anyway and which can be handled by how many servers you want.
Rails is great for a world where an app was running on one server, but that world just isn't there anymore as much as it used to.