4 ms·
I liked the line: _We build a layer on top of that shim that better exercises Ruby's potential, or we help build a new wrapper to replace the old._ I think thi
by jwilliams 18y ago
I liked the line: _We build a layer on top of that shim that better exercises Ruby's potential, or we help build a new wrapper to replace the old._
I think this is a great idea - it's the ultimate technical jujitsu. Take the weight behind Java and use it to give you a leg up.
The org I'm at is attempting something similar at the moment.
Course. Getting the wrapper/interface right becomes pretty important, but this is always the case.
- BrandonM 18y agoAgreed. 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.