4 ms·
Google is externalizing a lot of tools used internally for years. Use them or don't, it's your choice, but lots of time and effort has gone into making them wor
by dpe82 8y ago
Google is externalizing a lot of tools used internally for years. Use them or don't, it's your choice, but lots of time and effort has gone into making them work well so there's value there being made available for free.
To your point about .proto files for public endpoints: does every JSON HTTP endpoint exposed to the web provide documentation for you to build your own client? (of course not)
- deleted 8y ago[deleted]
- lost-theory 8y agoAgain, I don't think this specific example is hugely significant, I'm looking at the larger trend. Re: public endpoints. Say you're poking around a public web service, and it doesn't provide an API. Maybe you're writing a browser extension. Would you rather reverse engineer a JSON HTTP API with no documentation, or a gRPC-Web API with no .proto file?
- dilyevsky 8y ago$ grpc_cli ls <addr> You’re welcome.
- lost-theory 8y agoThat looks useful. Do you know if that works with gRPC-Web where the underlying gRPC port is behind a service proxy?