Re:Dear Slack: why is your WebRTC so weak?
by cpeterso on Thursday March 03, 2016 @04:16PM
(#11220099)
Summary: why does Slack support WebRTC in Chrome but not Firefox?
[ Parent
| on HN ]
Re:Dear Slack: why is your WebRTC so weak?
by TD-Linux on Thursday March 03, 2016 @04:28PM
(#11220181)
The article doesn't actually answer that, but it does point out some odd choices that make it suboptimal even in Chrome.
Re:Dear Slack: why is your WebRTC so weak?
by Klathmon on Thursday March 03, 2016 @06:32PM
(#11220884)
Well it's been a little over a year or so since i last worked with WebRTC, but portions of it have pretty bad cross browser compatability.
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.
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 …