Comments on: Hiding your Ruby behind Java interfaces

By: replicahandbags

replicahandbags — Mon, 19 May 2008 06:39:21 +0000

thanks for sharing,really enjoy reading your blog

By: Florin T.PATRASCU

Florin T.PATRASCU — Sat, 21 Jul 2007 01:31:30 +0000

In my case, still using JPublish ;) (http://code.google.com/p/jpublish/) and using Rails in the same time, having JRuby available for writing JPublish Actions for web development (http://weblog.flop.ca/2007/07/17/1184705235053.html) is a very nice feature. I respect Anthony’s opinion and I would do the same and remain happy in the world of Ruby, but there are situations when you simply have to use a java library because is part of a legacy system that you have to maintain (even though I requested the permission to rewrite that system in Ruby ;) Having JRuby, allows constrained Java developers to taste the sweetness of Ruby … so I am one highly appreciating the existence of JRuby.

By: Ola Bini

Ola Bini — Wed, 16 May 2007 02:37:32 +0000

Guillaume: Of course, we are bridging object systems. That’s the whole point of JRuby. If Ruby’s object system was the same as Java’s, we wouldn’t need JRuby at all. (blocks, closures, argument passing, method invocation, constant handling, module mixins are all parts of the object system, of course).

That said, if Dion had used BSF or JSR223 to do the invocation, those parts wouldn’t have been visible.

By: glud

glud — Mon, 14 May 2007 18:56:44 +0000

Craig Habuma blogged injecting Ruby (or Groovy) implementations of interfaces with Spring, in case you find yourself infiltrating a java team that also uses Spring.

http://www.jroller.com/page/habuma?entry=spring_meet_ruby

By: Guillaume Laforge

Guillaume Laforge — Mon, 14 May 2007 18:43:19 +0000

It would be really magic if the so-called magic line wasn’t needed. On the contrary, here, it shows that Ruby and Java are just bridged and not really integrated nor share the same object models.

By: Anthony Eden

Anthony Eden — Mon, 14 May 2007 17:15:25 +0000

I’ve been down this path before and I can tell you that context switching between languages can be very, very painful. Perhaps it doesn’t seem that bad to you but consider that other developers may have a tougher go at it. I used to build webapps with JPublish where the actions were all implemented in Python. Eventually I got to the point where I just switched everything to Beanshell because it gave me the benefit of a scripting language while at the same time providing a much easier path to convert code to Java when performance was critical.

Just a thought. Personally I don’t see Ruby deployment issues as such a big deal, so I can’t see myself using JRuby unless there was a library in Java that I absolutely *had* to have.