Additional Thoughts on Why Ruby isn't ready for the Enterprise...
I 'm still not going to respond to the complete (longish) article.
First, some agreements,
Ruby is going down a path of creating their own Virtual Machine. It seems to me, that they should simply put Ruby on the Java VM and not waste efforts in reinventing the wheelVM. Sure. Whatever good stuff that comes. What's for keeps is the Rubylanguage. Avi Bryant had even contemplated [mp3] that its highly possible having Smalltalk VM (more mature) running Ruby code. Heck, why not?
Ruby needs to address multilingualization quicklyi18n. Definitely. Don't be so sure it ain't coming or nearing. Anyways my 2 cents is, I haven't seen any i18n done right (read: development phase). Runtime support for i18n is mature, and that's the easy part.
Now the negatives,
Ruby seems to be missing something that is otherwise fundamental in other languages which is support for Regular ExpressionsHoly cow! Missing regular expressions in Ruby? That's funny. Firstly, its a common complain that Ruby inherited lots of stuff (good and bad) from Perl, guess what's included? My other 2 cents says that Java happens to have the worst regex support. Of cos, I'm talking about syntax.
I also couldn't find the equivalent of instance variables. Wouldn't that make reuse at an enterprise-level somewhat problematic?
Shouldn't the notion of methods being public, private and protected also be a part of every modern language?Missing instance variable? Notion of public, private and protected methods? Boy, this guy needs to sit down with Bruce Eckel (Nothing against Bruce, just thought its a funny de ja vu) Or more accurately, sit down with Ryan Davis.