News for hackers. Stuff that matters.
Re:Using Protobuf instead of JSON to communicate with a fron... by caust1c on Friday June 05, 2015 @12:45PM (#9666483)
> Message field names are mapped to lowerCamelCase

Why is a mapping to camel case necessary? I imagine it creates the potential for collisions, no?

Re:Using Protobuf instead of JSON to communicate with a fron... by iagooar on Friday June 05, 2015 @02:38PM (#9667194)
It's called "sadCamelCase", as opposed to "HappyCamelCase" ;)
Re:Using Protobuf instead of JSON to communicate with a fron... by wora on Saturday June 06, 2015 @11:30AM (#9671101)
Co-author of proto3 here. The reasons we chose lowerCamelCase are compatibility with Google's REST APIs (like Gmail API) and readability for users who work with JSON output directly without client library. API designers should not define confusing data schemas, let alone allow collisions. Most proto messages have small number of fields, avoiding name collision is a trivial for an API designer.
Re:Using Protobuf instead of JSON to communicate with a fron... by haberman on Friday June 05, 2015 @01:24PM (#9666704)
I think this may be to maintain style conventions with JavaScript and previous versions of Google Cloud APIs which were all based in lowerCamelCase (not 100% sure though, don't quote me on this).

A benefit of this decision is that if you create JSON manually in JavaScript (ie. without a protobuf library) your JSON objects will match JavaScript conventions.