3 ms·
Speaking of gRPC, it's unfortunate that they went all-in on HTTP/2. Should have made it work over HTTP/1.1. I know others made it work, but it wasn't first-part
by frollogaston 2y ago
Speaking of gRPC, it's unfortunate that they went all-in on HTTP/2. Should have made it work over HTTP/1.1. I know others made it work, but it wasn't first-party. Maybe it could've been more popular than JSON-over-HTTP by now.
- koakuma-chan 2y agoNo reason to choose HTTP/1.1 over HTTP/2.
- frollogaston 2y agoThe reason is that a lot of things don't support /2, ironically including Google's own AppEngine. Also Heroku.
- otabdeveloper4 2y agoNobody needs HTTP/2. It's just Google doing embrace-extend-extinguish of public domain protocols.