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.
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 stymaar on Thursday March 03, 2016 @07:12PM
(#11221059)
I've been working on a webRTC application as a full-time job for 1 and a half year now, and I've never faced cross-browser communication issues. The main problem at the moment is Chrome's implementation of the datachannel, it's terrible … (huge performance issues when having too many open connection, complete browser crash when using unreliable transport (fixed now, but it took almost one year), no support for Blob binary type …)
As the article says, doing Chrome-only webRTC in 2015 and 2016 is really a strange decision …
Re:Dear Slack: why is your WebRTC so weak?
by neximo4 on Friday March 04, 2016 @07:06AM
(#11223221)
Tried in 4 countries, Australia included. Granted its better and worse at times it is consistently worse off than using fb (via web browser), Telegram (Mac app) & Whatsapp (web app). They have a better architecture under the hood it looks like.
If the devs tracked startup times, they would know what exactly i'm talking about.
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
It's at less than 10% for most of the sites I manage, and steadily going down (apparently 14% globally).
Firefox can talk with firefox fine, chrome with chrome, but the 2 have some issues talking with each other.
Maybe Slack just made a decision to support chrome until the 2 meet in a way that makes them compatible.
seen a fair few negative posts of late.
If the devs tracked startup times, they would know what exactly i'm talking about.