Fine if you control the clients and the servers, but if you're writing your API for public consumption, API customers want REST not gRPC.
eg https://levelup.gitconnected.com/grpc-basics-part-2-rest-and...
We had the pleasure of working with some legacy SOAP recently - the other end had changed the WSDL such that our client no longer compiled from the WSDL - they couldn't work out what was wrong and where fearful of changing it again so we had to had to hand roll the client. Fun times....
I hope neither get as complex as SOAP - one of potential pitfalls of tooling is it becomes 'free' to add complexity.