Patrice Chalin

> @chalin doing this means we should also delete it from the grpc-go repo, which could unfortunately complicate the quick-start guide. What do you think? Actually, no. As is mentioned...

> > grpc/examples/route_guide.proto > > Darn. I missed that in #80. Neither of these example protos are in the correct directory. They should be in a directory that matches their...

- Moved proto into root-level `routeguide` folder, matching the proto's package name. - Added "The canonical version of this proto ..." message. @ejona86 @dfawley PTAL

> We can't currently have a separate proto root with Bazel. Ok, then that rules out having an `examples` folder. > I'm still opposed to having a top-level `routeguide` directory....

Any progress here?

>> Is the intention just to have something shorter > > That, ... The [Hello World client](https://github.com/grpc/grpc-kotlin/blob/master/examples/src/main/kotlin/io/grpc/examples/helloworld/HelloWorldClient.kt) is about 33 non-comment LOC. I'm not sure how much shorter it can...

Another thought that comes to mind: maybe a blog post (to be published at https://grpc.io/blog), covering the use cases that you mention, could satisfy your needs? cc @jamesward

As of 2022-08-14, here are the broken external links: ```nocode Non-OK status: 404 --- index.html --> https://twitter.com/grpcio request exceeded our ExternalTimeout --- docs/what-is-grpc/faq/index.html --> https://corner.squareup.com/2015/02/grpc.html request exceeded our ExternalTimeout ---...

> Ping on this @chalin. "[User-defined] Metadata is not _used by_ gRPC"? If @ejona86 is ok with that phrase (including the "User-defined" qualification", then it's ok with me.

From https://github.com/grpc/grpc.io/pull/499#discussion_r518440439: > There's _always_ been multiple gRPC languages with their own releases. Go and Java went public the same day C core did. I do not disagree with your...