Thanks John.  The water was definitely much less inviting the last time I stuck 
my toe in the JRuby pool.  I hadn't heard of TorqueBox but it definitely looks 
promising.  I'll probably set it up to serve our internal Rails applications 
and go from there.  

Andreas


On Dec 20, 2011, at 11:10 AM, John Lynch wrote:

> Andreas, I have worked on several JRuby apps that are in production, and I 
> would say that the best thing about JRuby is the  ability to deploy a 
> Rails/Rack app on "enterprisey" app servers. TorqueBox 2.x is my current 
> favorite, which is a nice wrapper around JBoss 7.  All the enterprise, none 
> of the XML.  Clustering is a breeze, and with InfiniSpan you get the 
> equivalent of a distributed memcached for free, plus built-in message 
> queueing and background jobs, etc. 
> 
> There are certainly rough edges that will cut you, but if you use Rails you 
> are used to that anyway.  Both JRuby and TorqueBox have full-time, paid 
> developers working every day on improving them.  On the small chance you find 
> a gem you cant use in JRuby, there is certainly a Java jar you can use 
> instead. If you think Ruby has a robust gem ecosystem, wait until you see 
> what Java has to offer.
> 
> Bottom line is, come on in, the water's fine!
> 
> Regards,
> 
> John Lynch
> [email protected]
> 
> 
> 
> 
> On Tue, Dec 20, 2011 at 10:02 AM, Andreas Kirn <[email protected]> wrote:
> "Compared to JRuby on Java 6, JRuby on Java 7 without invokedynamic is around 
> 25% faster, and JRuby with invokedynamic is nearly 3 times faster."
> 
> http://blog.jruby.org/2011/12/getting_started_with_jruby_and_java_7/
> 
> I think it's time to give JRuby another try.  I dismissed it as buggy and 
> irrelevant when I first played with it a few years ago, but it's starting to 
> look more and more interesting.  Does anybody here use JRuby in production?  
> Any war stories to share?  Bugs? Gem support issues?
> 
> Thanks,
> 
> Andreas
> 
> -- 
> SD Ruby mailing list
> [email protected]
> http://groups.google.com/group/sdruby
> 
> 
> -- 
> SD Ruby mailing list
> [email protected]
> http://groups.google.com/group/sdruby

-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby

Reply via email to