From: Robert Dober Date: 2009-04-14T19:51:11+09:00 Subject: Re: Ruby vs. Groovy: your perspective On Tue, Apr 14, 2009 at 10:23 AM, Michael Neumann wrote: > On Tue, 14 Apr 2009 17:11:58 +0900 > Albert Schlef wrote: > >> Eleanor McHugh wrote: >> > Well I'll concede that the JVM does have a few things going for it, >> > but I never was entirely comfortable with having my code tightly >> > coupled to it. >> >> When you're writing in Ruby, your programs are tightly coupled to the >> Ruby interpreter. Why is that better than having a program coupled to >> the JVM? > > Ruby is open-source. Ruby runs everywhere. Well so is the JVM, open source and run everywhere :). But to add to your answer, it is better to be coupled to Ruby than to the JVM, because you are one abstraction higher and although JRuby is a great thing to use you do not depend on the JVM, which is good. If use JRuby because you depend on Java features you do not loose anything, because you are bound anyway. If you use JRuby for other reasons you will not be bound to JRuby and can use any other rubyspec compliant implementation :). Robert -- Si tu veux construire un bateau ... Ne rassemble pas des hommes pour aller chercher du bois, préparer des outils, répartir les tâches, alléger le travail… mais enseigne aux gens la nostalgie de l’infini de la mer. If you want to build a ship, don’t herd people together to collect wood and don’t assign them tasks and work, but rather teach them to long for the endless immensity of the sea. -- Antoine de Saint-Exupéry