Still working on this? (Also: contact info) about capnp-ruby

[sogamoso]

👍

[guilleiguaran]

@tarcieri agree totally on this!! 👍

[Spaceghost]

@tarcieri What about using FFI and not creating "Another damn c extension?" to quote @headius.

[tarcieri]

@Spaceghost the C++ implementation does not expose a C ABI, much less an "FFIable" one (i.e. it doesn't rely on the preprocessor)

I am a huge fan of FFI and used it extensively in RbNaCl however someone would need to create an FFIable C ABI to the C++ implementation first.

[findchris]

👍

[tarcieri]

There's a Ruby GSoC project underway to build a C wrapper around capnproto's C++ implementation and then re-wrap that in FFI. We'll see how it goes.

[findchris]

Thanks for the update @tarcieri. Sounds promising.

[peakxu]

@tarcieri, would you happen to know how the Ruby GSoC project went? Also progress on making an implementation that works for JRuby?

[tarcieri]

@peakxu last year's project didn't go so well, but there's another GSoC effort this year

[ermanc]

@tarcieri any chance you know how 2016 GSoC effort went?

[tarcieri]

It went well, I think! It should now support RPC:

https://github.com/nemoNoboru/capnp-ruby

Perhaps it should be moved to https://github.com/capnproto

cc @kentonv @nemoNoboru

[kentonv]

@tarcieri Is it being used in prod? Is anyone actively maintaining it?

[kentonv]

(Not meant to be challenges, I'm just honestly curious.)

[tarcieri]

@kentonv not to my knowledge. I'm not sure people are actually aware of it.

All that said, I think it's the most complete implementation of capnp in Ruby to date.

[guilleiguaran]

I used it on production during a time but we stopped using capnp entirely because the libs for other languages that we were using were less mature (IIRC go and node)