Key Themes from the Discussion
-
Uncertainty about long‑term stability – Several users worry that relying on protobuf (or any “non‑standard” implementation) jeopardizes future compatibility.
"After gogoproto I'm hesitant to depend on another non‑standard implementation, ... can we be sure that it will still be around in 10 years?" — usrnm
-
Calls for a true, universally‑accepted standard – Participants question why protobuf isn’t formally standardized and note the proliferation of divergent “stand‑alone” implementations.
"why isn’t the following document a standard?" — squirrellous (referring to the protobuf encoding guide)
-
Appreciation for Buf’s ecosystem as a healthier alternative – Engineers from the protobuf team highlight that projects like Buf provide solid tooling and a clearer path forward, while still acknowledging Google’s long‑term commitment.
"Google can’t possibly fill all use cases… Kudos to Buf for making something that I'm sure a ton of people will find useful..." — esrauch (Google protobuf engineer)