|
|
|
|
|
by GauntletWizard
4112 days ago
|
|
The description language is oddly bulky and can't decide what order it's in. The api to open a connection is, again, needlessly bulky: I make a socket, I wrap it in a buffer, I wrap it in a protocol, I create a client using it, then I connect? There's the same level of complexity offered in grpc, but it's offered through an options object with sane defaults. There's no security protocol; or, if there is, nobody seems to use it. Is there an async call structure? If there is, nobody's ever heard of it. All the code I can find seems to be written at a preschool level. This may be due to working at a company that was an early adopter, or simply because the company is staffed by preschoolers. |
|
I think I preferred Google RPC, but it's not a huge difference to me.