The golang implementation of protobuf sucked historically (still does, but is improving) and gogo was an alternative that fixed a lot of problems and was nicer overall. Until its creator burned out and deprecated it. Chasing a constantly moving target that you have no control over is very taxing in the long run.
replyThis is concerning to hear. What do Protobufs accomplish, that requires them to be a constantly moving target?
replyhttps://www.youtube.com/watch?v=HTIltI0NuNg
replyI think it's less that protobuf is a moving target, and more that gogo tried to add in all the features that google didn't want to maintain, and learned that maintaining a massive feature matrix was impossible.
If I remember correctly, what finally broke the camel's back was the new API that Google introduced. But I may be wrong
reply