What are your complaints against it, if you don't mind my asking? The reason I ask is that after what I consider pretty careful evaluation of my own needs, I arrived at gRPC as the best solution. Of course it's not the best for every case, but surely there is a reason for its popularity.
I worked previously with REST/ GraphQL and they have everything I need. Easy way to mock the HTTP 1.1 protocol, easy way to write automation scripts, easy way to debug/customize. Easy for new developers since everybody uses HTTP 1.1. I work with Java and Spring and HTTP 1.1 support is OOTB. For GRPC you have limited tools and unofficial libraries.
When considering an alternative, I was thinking about REST / GraphQL over HTTP2, with a centralized "Type System" and generated models / code (basically GRPC but more user friendly). For me "sending a HTTP2 request with a json payload" seems better and more user friendly than "sending a grpc request"
But now that I looked a bit more into it, seems like HTTP2 might not have a lot of support, so do your own research.
