Hacker News new | ask | show | jobs
by drtse4 511 days ago
In my opinion, you shouldn't expose it to a browser, it's not what is good at, build something custom that converts to json. Like using REST to talk between backend services, makes no sense using a human readable protocol/api especially if there are performance requirements (not a call every now and then with a small amount of data returned).
2 comments
9rx 511 days ago
To be fair, it was intended to be for browsers. But it was designed alongside the HTTP/2 spec, before browsers added HTTP/2 support, and they didn't anticipate that browsers wouldn't end up following the spec. So now it only works where you can rely on a spec-compliant HTTP/2 implementation.
link
robertlagrant 511 days ago
The article seems to be an advert for this, with its plug of that hosted gRPC<->JSON service.
link