Agreed. Writing such a wrapper also introduces the possibility of someone later implementing the same library for Ruby itself. As long as the wrapper's interfac

Agreed. Writing such a wrapper also introduces the possibility of someone later implementing the same library for Ruby itself. As long as the wrapper's interface makes sense and the library is worthwhile, there is no compelling reason that the Java bits underneath couldn't be replaced by a C library and some glue code.