Link Details

While it's fun to bash ruby just for the knee-jerk fanboy reaction, this article offers little substance. Ruby is slow, RoR doesn't scale, little support by hosters. We've all heard that. Anything of interest, like exactly WHAT methods he had to code in C because ruby couldn't do it is left out.
And seriously, PHP instead of Ruby? Anything that is broken in Ruby (and that's quite a lot) is broken in a much more terrible way in PHP. Ugh.

As a Java fan boy I would have loved this article if content have done any justice to title

I love Java and several other languages. The only language I truly dislike is C++ which I wrote in for a number of years (ok, I am not a Perl fan, but neither am I proficient enough to pass judgement). Ruby is flexible and even elegant in parts, and it's sure a lot quicker to get the things that need to get done ... done than, for example, in Java. Rails is just a framework that is designed specifically with a small range of purposes in mind. As a new framework it does a pretty reasonable job (far better, in my opinion than any of the numerous Java frameworks my company tried) to get a straightforward task complete. If I worked for a bank, Java would be my choice. But I don't so RoR is working delightfully well for our current applications/ I have also used PHP, and it too, has its purposes. I would hate to think my toolbox were so limited that any single technology excluded all the rest. As the author of this silly piece starts out, he couldn't make his analogy of having a date with a hot chick work out. Nor could he make the argument work out.