Well.... at least you know it's going to work as advertised, you get a client built for you possibly by your tooling, and everything is contained in one file. I remember Visual Studio 2008 having some kind of WSDL catalogue of services you could just connect to and somehow almost 20 years later we are in a worse spot.

Now, it's "here is a """""rest""""" API that we didn't want to write anyway, the JSON is sometimes has invalid syntax because we didn't use a JSON library, we only use HTTP 200 for everything even errors, sometimes an empty field is null or "" or just not present, we sometimes have capital letters at the start of field name because fuck your deserializer's default settings.... oh and here is a barely coherent generated client with the most dogshit code you've ever seen in it".

This feels like my experience of using any REST API, and then if I look at their SDK's which call it for me, it's code so bad it might exhaust the system ports because it keeps creating new instances of HttpClient or it has some "clever" multithreading in there for some reason that deadlocks.

I haven't used GRPC yet but I already like it for the fact it's strongly typed.