3 ms·
Why isn't is suitable? (I've never used protobufs)
by positr0n 10y ago
Why isn't is suitable? (I've never used protobufs)
- skybrian 10y agoThe fields are indexed by field names (converted to lower camel case) instead of tag numbers. It's great for readability, but it's a lot more verbose, particularly for repeated fields.
- peq 10y agoI think the only reason to use json over the binary format is readability, so why care about this?
- ambrice 10y ago> Added a new field option "json_name". By default proto field names are converted to "lowerCamelCase" in proto3 JSON format. This option can be used to override this behavior and specify a different JSON name for the field.
- skybrian 10y agoRight, but nobody's going to set that for every single protobuf field.
- ambrice 10y agoYou're right. The only people that would use it are people that a) care enough about optimization to switch out shorter tag names and b) don't care enough about optimization to switch to binary format. Probably not many..
- skybrian 10y agoExcept everyone who is doing RPC in a browser. Not sure why that is, but binary formats aren't popular. We still care about performance.