I can't use something with a CoC.
Why not?
It's a political tool. It means they are into politics.
Prototool – A Swiss Army Knife for Protocol Buffers
31–40 of 66 posts
Re: Prototool – A Swiss Army Knife for Protocol Buffers
#32Earlier quoted context omitted.
> - a tee loadbalancer for gRPC, forwarding the same requests to both A and B backend pools, but only returning results from A. I don't think Envoy has this, but it should. Envoy can do this, via its shadowing feature. See the docs here: https://www.envoyproxy.io/docs/envoy/v1.6.0/api-v2/api/v2/ro... .
Great! I suspected it had to be in there, but it was hard to figure that through the docs. I didn't think of 'shadow' as a keyword, only 'mirror'. Thanks. One more reason to adopt Envoy and Istio.
Yeah, the docs are definitely an area of Envoy that could be improved. All the information is there, somewhere, but finding what you're looking for can be quite challenging.
Re: Prototool – A Swiss Army Knife for Protocol Buffers
#33Re: Prototool – A Swiss Army Knife for Protocol Buffers
#34Here are some other great tools that is quite useful with protobufs, one in C++ and one in pure javascript.
Re: Prototool – A Swiss Army Knife for Protocol Buffers
#35Re: Prototool – A Swiss Army Knife for Protocol Buffers
#36Earlier quoted context omitted.
Should you really be detailing the functionality of internal tools like this?
None of this is particularly secret. Any intern who worked at Google would have access to all this info. (Source: I'm a SWE at an Alphabet company)
interns still sign NDAs.
Re: Prototool – A Swiss Army Knife for Protocol Buffers
#37Re: Prototool – A Swiss Army Knife for Protocol Buffers
#38Earlier quoted context omitted.
It's a political tool. It means they are into politics.
How does that impact your usage of the project?
I don't want to deal with that. They are able to create problems artificially just to get power over you (on controversial topics).
IMHO people to avoid.
Re: Prototool – A Swiss Army Knife for Protocol Buffers
#39Earlier quoted context omitted.
How does that impact your usage of the project?
I don't want to deal with that. They are able to create problems artificially just to get power over you (on controversial topics). IMHO people to avoid.
From the position of a contributor, I understand and agree with you. You shouldn't contribute to a project whose terms you do not agree with, and I think that the "CoC" movement helps surface the type of organizational policies that a potential first time contributor would want to know before committing to the project.
I am curious to understand how it contributes to your decision not to integrate the tool into your workflow. I don't typically choose products based on the politics of the company that create them, which is the closest analogy I can come up with.
Re: Prototool – A Swiss Army Knife for Protocol Buffers
#40Earlier quoted context omitted.
Everything involves politics. At least they're being explicit about it.
No: physics, maths, cooking...
Oh please. Things involving more than one human invariably involve politics. Academics are just as susceptible as anything else, probably more so.
Cooking, if there is more than one person involved in preparing and eating the food, will involve politics.