I bought a Ruby book and flipped through some others. One thing struck me was the amount of time they generally spend saying "how great the language is" with hardly a word on "how the language is great". In fact they appear to deliberately dodge what's good about it and fail to address what's wrong with Ruby. Ruby is an object-oriented interpreted scripting language. Those last three adjectives are a big part of the proficiency gains. We know that on using a scripting language on the surface layer of an application has benefits. Ruby isn't any better than Groovy in that regard and the downside to a whole new syntax is obvious. The second leg of the two-legged-stool is Rails and its ability to generate the MVC artifacts for each page (no central controller). So instead using PHP or Perl it sure looks to me like Ruby is a winner. You get a nice MVC pattern generated for you. If you liked JSP 1.0 you will love the view template they provide you (gag me with a spoon). Clearly, Groovy and a few MVC generator tools are a better option, Grails for example. This way you can cleanly interface with type-safe, tested and optimized and reusable Java classes. I don't want to use Groovy for all my code and I sure as heck don't want to use Ruby on Rails. BTW, why does Java have so many more books than Ruby? Poor Ruby! They certainly must have all the facilities that the Java books represent, they just don't have any darn documentation. Too bad:) [img]http://antoniocangiano.com/images/rubybooks.gif[/img] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105822#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...