Ruby and ROR fanatics have adopted a highly annoying habit of luring hapless readers with highly provocative titles like "Ruby is not ready for production. Definitive proof". Let's really look at the reason why Ruby and ROR really sucks.

When you visit these bait articles you are flooded with inane logic and ridiculous ridicules which tries to ultimately prove why Ruby & ROR are the next best thing after sliced bread. So I adopted their strategy to lure readers with a real post to tell the top reason why Ruby really sucks.

Ruby sucks because of its fanatics who spend all (disputable) their waking hours trying to espouse the "greatness" of ruby and ror.

To quote one such recent "Ruby sucks" baiting blog article:
"Now we can start getting work done, and sharing real experiences on solving real problems."

I wholeheartedly agree with him. Let's all start doing real work instead of writing yet-another-ruby-sucks-bait-post (and another post ridiculing all of them).

And as for Ruby sucks theory - it does. Learn to live with it :)

PS. That really felt good. OK let me say it once again - Ruby and ROR sucks.

PPS: This post is targeted solely for Ruby & ROR fanatics. Flame > /dev/null

For the rest: I think Ruby and RoR is yet another framework with its own set of advantages and disadvantages. I have tried both and it didn't suit my requirements at that time. So far I have nothing to complain about Java along with my set of custom developed reusable libraries. You would salivate if I told how easy I have it going here.