It's amazing how much work these days goes into re-inventing RPC.
HTTP API's, whether using JSON as the data encoding or not, is basically RPC. Celery is decentralized RPC. AMQP is decentralized, unreliable RPC.
It's even a buzzword: microservices are basically "let's use RPC as much as possible".
Anything highly-distributed evolves towards explicit message passing, which is basically... yep, RPC.
You would think we'd have come up with a semi-reasonable general solution by now.
@icefox CORBA!! *grins manically*
@kara I am aware of CORBA! I even tried to use it once. It is even worse than OAuth.
@icefox I did QA for a small firm in San Diego, ages ago, that was making CORBA implementations. that's my sole exposure *chuckles*
@kara CORBA seems pretty much par for the course for things designed by committee in the 80's and early 90's, like Common Lisp and X11.
"Sort of does the important things but nobody ever actually *wants* to use it."
The Right And Virtuous Path is to take the things that are simple and nice, so people actually *like* using them, and make them incrementally powerful enough to do the Hard Things.
Start with JSON. Then JSON schemas. Then JSON-RPC. Then CBOR. And so on. Incremental improvement.
@icefox Hey, I sorta like Common Lisp!... at least, the tiny subset of it that I ever used. but clean and simple and nice it is not
@kara Common Lisp has many virtues but a masterpiece of cunning and integrated design it is not.