Comments on: You’ve Got Java in My Ruby

By: William Lightner

William Lightner — Fri, 14 Oct 2011 03:35:00 +0000

Anonymous classes are avoided for more reasons than their verbosity. Each invocation of an anonymous class instantiates a new copy of the class with a new ‘internal’ name, and these are not released by garbage collection. This means that in server-type applications that are up for long periods of time anonymous classes are a memory leak in ‘perm’ memory. They will eventually bring the VM down.

By: Thomas Enebo

Thomas Enebo — Wed, 09 Sep 2009 07:44:22 +0000

@Jay – I am not sure whether I would recommend jmephysics or not. It seems to be stalled at the moment. I am using a svn checkout of jmephysics and I have not seen a commit in a long long time (or ever? :) ). However, it does seem to work well enough with jme2, so it may suite your needs.

By: hosiawak

hosiawak — Wed, 09 Sep 2009 06:35:48 +0000

This is great, keep up the good work guys.

By: Phil

Phil — Wed, 09 Sep 2009 03:26:32 +0000

Good stuff. When I was working on my clojure-gem in JRuby I started out creating all my own proxies for the Java-implemented Clojure data structures, and then I realized–hey, JRuby is already constructing proxies for me; why not just modify those? It made the whole thing much easier to work with.

By: Ikai Lan

Ikai Lan — Tue, 08 Sep 2009 22:41:09 +0000

Knodi, what do you mean when you ask for fork support? Spawn a separate JVM? Or do you want something that can act as a daemon?

MRI Ruby uses Fork essentially because green threads aren't great for a variety of reasons I won't get into, but the JVM is really good at making use of multicore machines.

By: Knodi

Knodi — Tue, 08 Sep 2009 22:15:50 +0000

Fork support in jruby pls.

By: Jay McGavren

Jay McGavren — Tue, 08 Sep 2009 21:43:25 +0000

That's JME Physics 2 in the DSL example, right? Is that the recommended library for people wanting to do 3D physics in jRuby?

By: ahoward

ahoward — Tue, 08 Sep 2009 17:28:53 +0000

killer stuff guys – keep up the great work. your obsevations on the importance of blocks in a language wrt to keeping code DRY is spot on. surprising more languages don't realized this.