3 ms·
There are implementations that don't use libwebrtc/Chromium at all like pions-WebRTC[0] Or do you want something that has a completely different API? It would
by Sean-Der 8y ago
There are implementations that don't use libwebrtc/Chromium at all like pions-WebRTC[0]
Or do you want something that has a completely different API? It would be nice to be able to ignore the JS idioms, but it is tough to start from scratch.
[0]https://github.com/pions/webrtc https://github.com/pions/webrtc
- shazow 8y agopions' webrtc is the only third-party implementation with that level of completeness, and it's not very complete yet. It's super new (months old), but it's exciting! See issues: https://github.com/pions/webrtc/issues https://github.com/pions/webrtc/issues There are many aspirational repos that have been started over the years with the intention to implement WebRTC but very few of them actually made good progress. I too would love more third-party language-native implementations. Right now everyone is binding to the C++ codebase. The real problem without having language-native implementation is that it creates a protocol rift. Things like BitTorrent vs WebTorrent, or IPFS native vs IPFS JS: It's effectively UDP/TCP vs WebRTC, clients on one end (native apps that aren't NodeJS) can't speak to clients on the other end (browsers) without a relay bridge (which is always NodeJS).