undefined | Better HN

0 pointsgothack6y ago0 comments

Partly down to the branding of the project, and the perceived added complexity which was not required, I just wanted a a simple extensible RPC mechanism, not a "Infinitely faster" "cerealization protocol" with "time travel" and "distributed objects". Cap'n proto is a lot to take in and wrap your head around.

Edit: I didn't "stop" with cap'n proto, I never started because the project rubbed me the wrong way :/ maybe I should have given it a go, but heh, I made a thing instead.

0 comments

1 comments · 1 top-level

kentonv6y ago

Heh, fair enough. The branding is just meant to be silly (and to make fun of misleading benchmarks) but I totally get how it might be off-putting to some.

FWIW the Cap'n Proto C++ implementation ought to be able to layer on top of vsock pretty easily. You can pass an arbitrary kj::AsyncIoStream to capnp::TwoParty{Client,Server}, and you can construct an AsyncIoStream wrapping any socket file descriptor.

But yeah, capnp RPC is definitely one of the more complicated RPC implementations out there and if you don't need that power it may be too much.

j / k navigate · click thread line to collapse