WebRTC doesn't give up on late audio. This isn't factually correct. WebRTC has NACKs[0]. The receiver (AI Inference server) decides when to either accept the gap in RTP packets or if it sends the NACK and waits.
This article doesn't describe how Voice AI systems I work on operate. For speech-to-speech I am working at 20ms/200ms chunks and doing inference. So I don't want buffers
[0] https://webrtcforthecurious.com/docs/06-media-communication/...
You can have opus in-band FEC as well, though he mentions it in the article too.
What I find frustrating about these sales pitches that conflate the different parts of WebRTC. WebRTC is protocol, sdk/software and a API in the browser. So if one part has an issue it is important to explain it with detail.
It's like attacking HTTP by saying 'HTTP is bad because this server doesn't have Y setting'.