errors for arjdbc tests on mysql all look similar
there may not be too many changes needed to get these suites running nearly green
drbobbeaty has quit [Ping timeout: 272 seconds]
drbobbeaty has joined #jruby
headius: I had lunch with Josh Haberman yesterday. You may remember him from this comment thread from ~8 years ago where you were both actively discussing the tradeoffs of FFI versus extensions https://github.com/protocolbuffers/protobuf/pull/121
The subject of using FFI in the Protobuf gem has came up again internally. Since I'm also about to break ground on a technical design doc for how to build JRuby support for the gRPC gem, I'd love to get your take on whether FFI might be a better solve.
If I'm understanding the core concerns from the ancient thread, the reason that Protobuf team didn't elect an FFI-based solution back in 2014 was because of memory management concerns. They pointed to the fact that the performance-focused JSON gems didn't use FFI.
In the years since - has FFI gotten better at the use case where the concerns were focused - processing potentially huge trees of nested structures and "doing the right thing" with memory management when (only) arbitrary parts of the tree remain referenced by Ruby?