Agreed! I like grpc for the same reason. If I need to work with REST, a schema-first approach is ideal as it means various client, server, validation, and docum

Agreed! I like grpc for the same reason. If I need to work with REST, a schema-first approach is ideal as it means various client, server, validation, and documentation dimensions are in sync by default. I get why folks often come at it from the other end and just layer some swagger annotations on top of their existing server code — lack of experience, the dynamicist’s mistrust of typing in general, or maybe they’re in a niche stack without a workable binding generator. Still, it’s better for everyone if the API provider can pull off the artifact-driven approach.