4 ms·
Why is gRPC considered bad? I can understand that people who are used to HTTP based APIs will feel more comfortable being able to tap into a rich fauna of tool
by bborud 6y ago
Why is gRPC considered bad?
I can understand that people who are used to HTTP based APIs will feel more comfortable being able to tap into a rich fauna of tooling for HTTP.
However personally I am not really interested in raw network APIs as long as they work. I'm interested in programming - not poking around low level stuff.
I'm interested in libraries for speaking to services. When I use services like Twilio and Stripe, I'm not interested in rolling my own. I'm not going to implement my own unless I really have to. It isn't nice to just publish an API and not have libraries for talking to them.
gRPC, at least for me, makes both initial bootstrap, development and maintainance easier.