4 ms·
Might it be though? Protobuf's tooling seems like a byproduct of the fact that you can't read protobuf and it's strict and type safe enough that you can generat
by maxmcd 6y ago
Might it be though? Protobuf's tooling seems like a byproduct of the fact that you can't read protobuf and it's strict and type safe enough that you can generate lots of things.
Ion is readable and (seemingly) not very strict about schema. Seems like that would not readily incentivise additional tooling.
- devxpy 6y agoProtobuf can be converted to (and from) JSON for readability
- vii 6y agoProtobuf actually has a canonical text format. It's easy to produce in C++ or Java https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.text_format https://developers.google.com/protocol-buffers/docs/referenc... The format has much less extra syntactical noise than JSON. For example, name: "vii" # comments allowed! id: 23923373 Pretty nifty as it allows readable configuration files with structured data.
- tandr 6y agoif it is an "easy to produce or consume in language X" it does not mean it is canonical - it means that language X has an extension that allows to do so. Is there a place in protobuf spec or documentation mentioning this to be a part of the protocol?
- vii 6y agoLanguage X is at least C++ (as linked), Java https://developers.google.com/protocol-buffers/docs/reference/java/com/google/protobuf/TextFormat https://developers.google.com/protocol-buffers/docs/referenc... , and Python https://github.com/protocolbuffers/protobuf/blob/master/python/google/protobuf/text_format.py https://github.com/protocolbuffers/protobuf/blob/master/pyth... I think the Protobuf spec focuses on the binary serialization - the text format and JSON representations are not related to that at all, of course.