Ruby and Rails on JVM

Hi, sorry if this is OT. I wanted to if there are any limitations of jRuby. The community does not discuss this much and i feel its not used that much. What are the reasons?

Thanks,
Adi

Adi wrote:

Hi, sorry if this is OT. I wanted to if there are any limitations of
jRuby.
The community does not discuss this much and i feel its not used that
much.
What are the reasons?

Although your question is somewhat off-topic for this forum, since it
should be directed to a JRuby forum, I'll provide my two cents.

AFAIK the primary limitation of JRuby has to do with gems that use
native C extensions. I believe that a good number of the most popular
gems have already been ported over to Java extensions.

Given this limitation, it also means that JRuby gains access to a lot of
Java code, in a more direct manner than C based Ruby implementations.

Why the interest in JRuby?"

What is your end goal?

Do you have some existing Java code libraries that you want to access
from your Ruby on Rails application?

Are you in a "Java shop" and are attempting to "sneak" in some Ruby on
Rails without disrupting your current deployment infrastructure?

These are all good reasons to consider JRuby. The team building JRuby
seems to have made significant progress. I haven't looked at it lately,
so I don't know how far along they are with Rails 3.0 support. But, they
seem to have built a fast, reliable Ruby implementation.

Rails 3.0 has been designed to work with Ruby 1.8.7, Ruby 1.9.2 and JRuby 1.5.2+ as you can read in the blog post that announces the Rails 3.0 release :slight_smile: