JRubyArt-0.3.0 vs ruby-processing-2.6.12

Previously I posted a comparison between a different version of JRubyArt and ruby-processing where both were running using processing-2.2.1 and the the same version, but they had different designs. The current JRubyArt candidate is more similar to ruby-processing, but is targetting processing-3.0 (currently 3.0a10) and jruby-9.0.0.0 (currently jruby-9.0.0.0.rc1). I see ruby-processing as sticking with processing-2.2.1, but remaining compatible with stable releases of jruby, whereas JRubyArt will only be compatible with processing-3.0a10+.

External Dependencies

• ruby-processing requires an installed version of processing-2.2.1
• ruby-processing requires an installed version of processing-3.0a10+

Core processing libraries (sound, video etc)

• ruby-processing has builtin support 
• jruby_art has the same built in support but sound, video libraries are now external (since processing-3.0)

Contributed processing libraries

• ruby-processing has builtin support for libraries installed by processing ide 
• jruby_art has the same builtin support for libraries installed by processing

Vec2D, Vec3D, Arcball and DEGLUT

• ruby-processing requires load_library 
• jruby_art these libraries automatically loaded into jruby runtime

Processing::Proxy module

• in ruby-processing Proxy can be used to mimic processings inner classes, probably v. bad juju convenience isn't everything 
• in jruby_art a different Proxy can also be used to mimic processings inner classes but has a simpler implementation