The tricky part is not the technical transition itself, it is how you communicate it. Hiring managers and recruiters often pattern-match on tech stacks: they see "20 years Ruby" and mentally put you in a box. The real skill is reframing that experience so the architectural depth comes through, not just the language.
I have been thinking about this problem a lot — how do you help developers articulate what actually makes them valuable when they switch contexts? I built a tool (https://super.myninja.ai/apps/6de082c7-a05f-4fc5-a7d3-ab56cc...) that uses AI to help reframe experience for different roles and tech stacks. It has been interesting to see how much better "20 years building production systems across Ruby and C#" reads compared to "Ruby developer now doing .NET".
Nowadays C# is anyways much more expressive than before. Meanwhile Ruby is still very slow.
Not to mention how poorly maintained are most Rails projects. People have been "vibe coding" forever.
A well-organized and maintained Rails app is great though. I'd definitely consider working with it again, but it really depends on what company it is.