3 ms·
I did read the link and I was at Google at the time people started arguing for that. With respect, I think the argument was and still is incorrect, that the wro
by mike_hearn 3y ago
I did read the link and I was at Google at the time people started arguing for that. With respect, I think the argument was and still is incorrect, that the wrong lessons were drawn and that proto3 is worse than proto2.
- klabb3 3y agoAlright, fair enough. Apologies for the dismissive tone. Could you elaborate (or point to) these wrong lessons or an alternative?
- hgsgm 3y agoOK, what do you do when a message comes in missing a field? Crash the server?
- dastbe 3y agoyou reject the message in the framework? and if the client is aware it’s required they fail to send? the bigger challenge with proto3 is that people use it both for rpc and storage, in some cases directly serializing rpc payloads. Disregarding how awful a choice that is, you likely want to trade off flexible deserialization of old data at the expense of rigidity, and conformance.