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'.
But the default WebRTC client is the one that browsers use. If Y setting isn't in that client or even if it is in the client and not enabled in the browser, it's basically as if WebRTC didn't have that at all. It would be like saying 'SSH is bad b'c OpenSSH doesn't have Y setting' b/c the vast majority of clients/servers are OpenSSH.