Pretty sure that guarantees you'll get watered down answers for the rest of the survey... At least, I'm not comfortable associating my company with Ruby advocacy/disparagement.
That plus its good community, long time existence, low defect rate with static analysis tools (i.e. Coverity), and increasing usage in mission-critical applications (eg Bank of America). Seem like an excellent baseline until something better comes along. Plus, if your writing business code, there's a good chance what you write might stick around for a decade or more. I pity the poor soul that would be reverse engineering Java, C#, etc code to support and extend legacy 10 years from now. Python with decent documentation might be way easier on them, though. :)
I see ruby occasionally in system administration and DevOps tooling but apart from puppet and homebrew there's nothing I would recommend to anyone who isn't already interested in going all-in on ruby development.