7 comments

[ 4.9 ms ] story [ 24.0 ms ] thread
What does varlink do that grpc or capnproto don't offer? Hell, it doesn't even seem much batter than openapi...
Huh, that way of doing asynchronicity is quite interesting.

Though my Haskell and Rust primed brain really dislikes the way ownership of the memory allocation for the response struct works.

It gets allocated by the caller (library), handed over to the function fully owned, and then gets consumed by the response function?

I'm wondering why Varlink, while incredibly similar to JSON-RPC, is designed to be incompatible with it?
json, rpc, and that uint64_t bit integer
So, there's another copy of CORBA. :-)