> However, building the WebRTC component is not trivial. It requires a lot of system resources, downloading many gigabytes of source code, and the process uses some Google-specific build tools.

Ouch. I wonder how much of that is actually necessary to implement webrtc though, maybe a lot of it could be trimmed out? If the standard really is that complex, it's a pretty strong argument against it.

This is a Google problem, not WebRTC.

I have been using webrtc.rs on iOS. My build is ~2Mb and takes me ~3 min to build.

Yeah, Google really takes NIH to another level - you need to set up a different build chain specifically for Google-written dependencies.

It’s a shame :/

I am a big fan of WebRTC. The conflation of WebRTC and Google’s implementation hurts a lot.

Really excited to see how much webrtc-rs has progressed. The next 3 years are gonna be really interesting

I understand, but to be fair Google's implementation were the only one available for a long time that I fear that webrtc-rs would need to be bug-compatible with it.

F-Droid being alarmist? Nothing new under the sun.