From: Lionel Bouton <lionel-subscription@...>
Date: 2007-11-10T09:35:02+09:00
Subject: Re: enterprise ruby

Robert Klemme wrote the following on 09.11.2007 22:05 :
>
> Personally, if I had the resources to invest into this I'd rather
> spend them on JRuby.  You get a GC with many tweaking options etc.
> plus native threads.
>

Please don't forget that many gems still don't work or don't have
replacement in JRuby. JRuby is *the* solution for people needing easy
Ruby <-> Java integration but Ruby with strong Unix ties has its
benefits too.

I think I'd have to spend quite some time to migrate applications from
MRI to JRuby: I heavily used ruby-gettext, hpricot, memcache,
ruby-opengl and I believe most of these use C for library interfaces or
performance... some utils like rcov probably don't work either with
JRuby because they probably rely on the same C interface.

So as much as I'd like JRuby to succeed even if I don't use it myself
(currently), people willing to work on MRI (or YARV and Rubinious for
that matter) are most welcomed to do so too.

But maybe there is an efficient way to use JNI to trivially port most of
these to JRuby. This could motivate my toying with JRuby...

Regards,

Lionel