Re: [protobuf] Is protobuf3 a superset of protobuf2?

Thanks for your quick response Adam! Regards! On Tuesday, January 21, 2020 at 3:05:22 PM UTC-3, Adam Cozzette wrote: > > Right, we are still maintaining both proto2 and proto3 and plan to keep > supporting both flavors indefinitely. > > On Tue, Jan 21, 2020 at 4:09 AM Luciano Perezzini >

Re: [protobuf] Is protobuf3 a superset of protobuf2?

Right, we are still maintaining both proto2 and proto3 and plan to keep supporting both flavors indefinitely. On Tue, Jan 21, 2020 at 4:09 AM Luciano Perezzini wrote: > This is still true, Adam? Google would not deprecate Proto2, and Proto2 > and Proto3 are just different flavors of Protocol

Re: [protobuf] Is protobuf3 a superset of protobuf2?

This is still true, Adam? Google would not deprecate Proto2, and Proto2 and Proto3 are just different flavors of Protocol Buffers? Me and my team are about to start a brand new project using Protocol Buffers and the lack of missing value check properties in Proto3 is a BIG concern. Thanks in

Re: [protobuf] Is protobuf3 a superset of protobuf2?

Yes, we are planning on supporting proto2 pretty much forever. Within Google we have a huge amount of code using proto2 and for the most part we're not attempting to migrate existing code to proto3. Language support is one reason to go with proto3, but it's also simpler and more convenient for

Re: [protobuf] Is protobuf3 a superset of protobuf2?

Adam, I understand there is no *current* plan to deprecate proto2. But is it really expected to be supported forever? If that's the case, I suppose the only reason to choose proto3 over proto2 (if you happen to want the features and semantics of proto2) might be that not all languages/runtimes

Re: [protobuf] Is protobuf3 a superset of protobuf2?

Actually we have no plans to deprecate proto2 and we are still actively developing it, so you can really choose either one without having to worry about support going away. On Sat, Dec 16, 2017 at 11:42 AM, Josh Humphries wrote: > I think proto3 was intended to be simpler

Re: [protobuf] Is protobuf3 a superset of protobuf2?

I think proto3 was intended to be simpler -- an evolution of protobuf in a direction that is more refined and elides superfluous features. Eventually (though not likely any time soon), support for proto2 will go away. The main omission in proto3 that I personally felt strongly about was the lack

Re: [protobuf] Is protobuf3 a superset of protobuf2?

Thank you everyone for all the great input! Based on this discussion, what is the advantage of using proto3? It appears that proto2 is more feature rich. JSON isn't a compelling reason Thanks -- You received this message because you are subscribed to the Google Groups "Protocol Buffers"

Re: [protobuf] Is protobuf3 a superset of protobuf2?

To clarify, proto3 supports extensions in that you can define custom options or create extensions for proto2 messages (since it is valid to import proto2 files). But it does not support defining an extendable message (e.g. no extension ranges can be defined with proto3). Proto3 is almost more

Re: [protobuf] Is protobuf3 a superset of protobuf2?

The main thing that proto3 lacks and keeps coming up every time I use it is field availability information. All the has_* API is gone for basic types, so you have to supply that information separately, or restructure your logic to not rely on it. -ilia On Fri, Dec 15, 2017 at 6:40 PM,

Re: [protobuf] Is protobuf3 a superset of protobuf2?

Neither one is really a superset of the other. Proto3 does not support extensions but uses the Any type as a replacement. On Fri, Dec 15, 2017 at 3:40 PM, ajcurtis84 wrote: > Hello, > > I have not found anything in the documentation that explicitly says this. > The only

[protobuf] Is protobuf3 a superset of protobuf2?

Hello, I have not found anything in the documentation that explicitly says this. The only indication is that the proto3 documentation refers to proto2. Things like extensions are available in the proto3 syntax? thanks -- You received this message because you are subscribed to the Google