Major Kudos.
Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
11–20 of 51 posts
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#12Given that they're both open source, built to the same open standard, and (at least nominally) completely interoperable, I'd say "complement" would be a better word than "rival."
It is generally considered a positive thing when proposed standards have multiple independent implementations.
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#13They open it after all the other browser vendors are already done with this task. Why haven't they released it from the very beginning, saving a few days work-time for others? I think that now it has almost zero value.
The README states the focus isn't on browsers > OpenWebRTC is built on the belief that the WebRTC standard would transcend the pure browser environment and that native apps, implementing the same protocols and API's, would become an important part of the WebRTC ecosystem and it has out of the box platform support for iOS and Android
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#141. A better headline would be "Ericsson open-sources another WebRTC implementation". WebRTC is a set of standards, and they are implementing them, which is one of the purposes of having standards: to have multiple implementations.
2. One of the purposes listed by Ericsson for having another implementation is to "transcend the pure browser environment and that native apps ... would become an important part of the WebRTC ecosystem". What I would like to point out is that the implementation of WebRTC found at webrtc.org (ie Chrome's implementation) already supports mobile and native apps. In fact, the documentation is linked to right from the front page:
http://www.webrtc.org/reference/native-apis
And there are lots of native/mobile apps that already use it.
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#15One of the biggest issues in the whole WebRTC process has been getting companies to commit to documenting the minimum SDP for interop. I'm curious how well these two implementations will interop. One of the reasons for ORTC is to remove signaling from the specification.
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#16Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#17For those interested in Google's implementation: https://code.google.com/p/webrtc/source/browse/#svn%2Ftrunk%... or browse the code: svn checkout http://webrtc.googlecode.com/svn/trunk/ webrtc-read-only Also Ericsson's code is on github (I couldn't find a direct link from the parent article): https://github.com/EricssonResearch/openwebrtc/
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#18Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#19For those interested in Google's implementation: https://code.google.com/p/webrtc/source/browse/#svn%2Ftrunk%... or browse the code: svn checkout http://webrtc.googlecode.com/svn/trunk/ webrtc-read-only Also Ericsson's code is on github (I couldn't find a direct link from the parent article): https://github.com/EricssonResearch/openwebrtc/
code.google.com - ugh why can't google admit defeat and start using github?
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#20Earlier quoted context omitted.
code.google.com - ugh why can't google admit defeat and start using github?
They already did. New projects are on Github, and they seem to be migrating old ones: https://github.com/google .
https://github.com/GoogleChrome/webrtc/tree/master/samples/w...