> even in go its a pain in the ass to have to regen and figure out versioning shared protos and it only gets worse w each additional language The secret is: do

> even in go its a pain in the ass to have to regen and figure out versioning shared protos and it only gets worse w each additional language The secret is: don't worry about it. There is no need to regenerate your proto bindings for every change to the protos defs. Only do it when you need to access something new in your application (which only happens when you will be making changes to the application anyway). Don't try and automate it. That is, assuming you don't make breaking changes to your protos (or if you do, you do so under a differently named proto).