The whole streaming gRPC for browsers story is indeed a rather interesting (and sad) one. Around 4 years ago this seem to just have been blocked on the browsers missing some APIs for streaming HTTP bodies instead of waiting for the whole response to complete.
The situation there still doesn't have changed if I read that thread correctly - but instead of adding those APIs there is now talk about using completely different technologies and yet another set of non-available APIs? That doesn't make a lot of sense to me.
And while WebRTC (or using a not-yet-specified protocol on top of QUIC) might be rather cool POCs, those throw a lot of complexity at a workaround for a problem which seems to have a far easier solution (get the required APIs implemented).
The situation there still doesn't have changed if I read that thread correctly - but instead of adding those APIs there is now talk about using completely different technologies and yet another set of non-available APIs? That doesn't make a lot of sense to me.
And while WebRTC (or using a not-yet-specified protocol on top of QUIC) might be rather cool POCs, those throw a lot of complexity at a workaround for a problem which seems to have a far easier solution (get the required APIs implemented).