bolkedebruin commented on PR #27468:
URL: https://github.com/apache/airflow/pull/27468#issuecomment-1308788256
I stand corrected, the AIP was there and I missed the voting. So any
argument I make below is mood.
The issue I find with JSON-RPC and with JSON in general is its lack of
strong typing (yes I know of JSON Schema, but that is like XML and XSL) and
that when thing become complex it starts becoming unreadable and you need a
seperate IDE/parser for it (ohhh I forgot a ","). It is great for public APIs
and interop but for internal ones not so much as you control both ends. This
means lack of maintainability ("ohhh you forgot to update the schema") for me
which trumps imho the readability over the wire part (as you control both ends
and can be enabled for debugging purposes wth grpc/protobuf). Too much stuff
happens at runtime rather than at compile time.
I have never been happy with any choice for JSON anywhere except public
facing APIs. Now I am gonna cry in a corner somewhere.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
