That's true, but you might be missing the productivity gains from using a framework like Ruby/Rails -- you can throw a lot of hardware at a problem for less than a single extra developer's salary.
Rails coders are more expensive than e.g. php coders. Given the same head count, a Rails shop will burn more cash. Many managers don't see productivity, but cost = headcount x salaries. It's the easiest variables for them to tweak to change their bottom line.
Of course, productivity depends far more on the quality of the programmers and coding practices of the team than the language. I'd take a team of kick ass php guys any time over a group of inexperienced/douchy rails guys, and I hate php with a passion. Ceteris paribus I'd go with Ruby.
(Come to think of it, it kind of reminds of the martial arts comparison mantra: "It's the quality of the individual practitioner that counts far more than his chosen style")
