3 ms·
> It isn't human readable This is a tooling problem. Wireshark can decode protobuf for you when you're inspecting gRPC traffic.
by ackfoobar 1y ago
> It isn't human readable
This is a tooling problem. Wireshark can decode protobuf for you when you're inspecting gRPC traffic.
- horsawlarway 1y agoNeeding that tooling is a format problem. JSON is bad at everything except being simple and easy. Turns out simple and easy is a real winner.
- nothrabannosir 1y agoJSON has one glaring flaw: nested json encoding in strings becomes awful to read. I encounter it too often in reality where individual layers use JSON, but want to support arbitrary strings in their API. Encodings which use prefix length don't suffer from this, which ironically even includes most binary formats.
- bluGill 1y agoBack to my main point though: normally I don't need the complexity that things like nested JSON would be. When you do though JSon is a bad format. (actually I would go so far as to say you never need something that complex - but the problems you are trying to solve with nested JSON are still complex enough that you should use a more powerful/complex framework, but better design of your data store would avoid the need for nested JSON.)
- bluGill 1y agoIf you have the correct version available. All to often when debugging problems the person in the field doesn't have the correct tools, or doesn't know how to use them (in this case you may not want to share the proto config with that person...) As such the less tools needed to understand something the better.