[mplewis]

Rails is unfortunately much slower, and it’s quite coupled to the concepts of server-side rendering and OOP MVC. Making Rails work with a modern frontend feels pretty hacky compared to using a full-stack TypeScript framework.

[silversmith]

I'll give you the slow, but "modern" frontend is a breeze. Webpacker (yes, the deprecated one, newer solutions are worse) handles React beautifully, and my graphql API definition gets seamlessly converted into typescript types. If anything, it often feels even easier than the code sharing I've experienced in node-land.

[samtheprogram]

What are you using for GraphQL support in Rails? I was just looking into this yesterday.

[gls2ro]

Because maybe other people might read this:

Rails are good enough to keep Shopify standing for another year of holiday sales. It seems to do that since 2006, so this alone demonstrates that Rails can support you a long way in your multi-billion business.

And if you think: "yes, but Shopify has a big talented team," I feel the need to say back, "Well, when you are at Shopify business size, you will have it too. And Shopify used it when they were small too."

I am not saying Rails fits everything, but if your business fits Rails, that is a great framework to build with.