News for hackers. Stuff that matters.
Re:Dear Slack: why is your WebRTC so weak? by dwwoelfel on Thursday March 03, 2016 @06:29PM (#11220873)
> you need to have a very good excuse to launch something with WebRTC and not support Firefox.

I built audio chat over webRTC for https://precursorapp.com [1]. I built support for both Firefox and Chrome, but I can understand why someone would choose not to support Firefox.

There are lots of annoying little differences between the two implementations. For example, Firefox wouldn't fire a negotiationneeded event after adding a stream [2], so I had to add a special workaround for them. Connection stats was another area where the APIs diverged a lot.

In their defense, sometimes Firefox does a better job of implementing the spec than Chrome does. But since most people develop in Chrome first, it's no surprise that they put off working on a Firefox implementation until they're happy with their implementation in Chrome.

[1] Click on the mic icon at the bottom left of a document to try it out.

[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1071643

Re:Dear Slack: why is your WebRTC so weak? by randall on Thursday March 03, 2016 @07:21PM (#11221096)
This is our experience too for Epishow. It's not that we couldn't get it working, it's that we focus on one platform (chrome) then expand outward (web at large, which for now means ff).
Re:Dear Slack: why is your WebRTC so weak? by GFischer on Friday March 04, 2016 @07:55AM (#11223422)
Another problem is that Firefox is losing market share badly.

It's at less than 10% for most of the sites I manage, and steadily going down (apparently 14% globally).