I can only answer by parable. Start from the point of view of a group of carpenters asking "is cardboard strong enough to build houses from" and you may a consensus until someone chimes in to say "but a lot of people have made a lot of money selling cardboard houses that survived just long to let them gather investors and money for building real houses." Sure, that may well be true but it's really going to change the view of carpenters.
And that cardboard house provided enough shelter for them to survive and at some point, go to the bank to get a loan for a bigger, sturdier house. I understand that Ruby can be an issue at some mega-scale, I've experienced how slow, memory-hungry and not a concurrency natural it can be. But the thing is, for 95% of the people building businesses, they don't need mega-scale. They just need enough. And Ruby on Rails provides just that. It's fast to build a platform with, it's easy to think about, it has a huge ecosystem and it's worked for a lot of people.
The owners of Twitter never had to worry about the shelter offered by Ruby-on-rails. The original system architect and his team hardly found shelter since he was replaced along with Ruby-on-rails.
But I think people still underestimate how much development isn't that. Most startups involve things that need to scale now or things that will need to scale. A lot of scientific development need complex algorithms. A significant portion of corporate development needs speed because it's operating at scale or because it's one piece of a long pipeline of import/export applications etc (another portion of corporate development doesn't need speed but good luck finding the discipline to get your manager to distinguish the two cases). And there's embedded and various other things.
"Don't worry about speed, we're just prototyping here" is a saying that always signals danger - a large organization often will want to deploy whatever monster once they know it works.
So really, it seems like Ruby is indeed great for apps for medium-sized brick-and-mortar business wanting a web presence and there is a whole lot of that happening. However, Ruby being inherently slow in multiple dimensions means it's dangerous for many other use cases (dangerous because of the "it works? Why not keep using it" factor and the danger being you'll wind-up using after its slowness becomes a real headache).