I've been using Rails since 2008, and participated in more than 100 projects in these last 10 years. Either by coding or managing them. Most of these were Rails projects. Moving to node is part of planning the tech that we're going to propose to our clients during the next 10 to 20 years.

I didn't conduct a thorough analysis on the reasons why I've seen big corps rejecting Rails, so what I'm about to say is based on the the experience of being through all these projects.

But most Rails projects are connected to the innovation departments and once they passed through the PoC stage, their IT departments asked for a re-write on a tech already in their ecosystem. Supporting additional techs raises complexity and forces them to support another stack.

We were indeed able to push some Rails apps to production on enterprises, but these were usually apps that performed a specific goal for one of the departments, and once we went for the big projects within their core, tech stack was always an issue.