3 ms·
Additionally, during the 3 years I've had experience with WebRTC, I've come across at least 2-3 browser bugs causing compatibility issues when connecting peers
by smaddock 6y ago
Additionally, during the 3 years I've had experience with WebRTC, I've come across at least 2-3 browser bugs causing compatibility issues when connecting peers cross-browser.
This is just not something you run into with WebSockets.
I'd recommend simple-peer for anyone who does choose to use WebRTC. The maintainers are usually able to smooth these issues out in a reasonable timeframe. <3
https://github.com/feross/simple-peer https://github.com/feross/simple-peer
- Sean-Der 6y agoI don't think the issues with WebRTC is the protocol, but the tooling. The community did a really good job of creating tooling for Websockets with stuff like https://github.com/crossbario/autobahn-testsuite https://github.com/crossbario/autobahn-testsuite. There is nothing like that for WebRTC. We tried to do it, but the IETF event was cancelled https://twitter.com/steely_glint/status/1230447935307026432 https://twitter.com/steely_glint/status/1230447935307026432. I am hoping that in the next 6 months we can have something like that so that all the WebRTC implementations will work together a lot better.