Slack: Other browsers require significant effort so we're focused on Chrome

Re:Slack: Other browsers require significant effort so we're... by ikonst on Saturday February 03, 2018 @02:37PM (#16299138)

WebRTC is somewhat new and complex, and browser support varies greatly. I don't know what kind of unlimited resources behemoth you imagine Slack to be, but I can definitely see how doing consistently working cross-browser WebRTC would be too much effort to be able to pull off at a given time.

[ Parent | on HN ]

Re:Slack: Other browsers require significant effort so we're... by pcwalton on Saturday February 03, 2018 @02:43PM (#16299171)

This is apparently largely because Chrome's implementation of WebRTC has been less standards compliant than that of Firefox. See https://twitter.com/adambroach/status/959298097674305537 (by one of the WebRTC developers).

[ Parent | on HN ]

Re:Slack: Other browsers require significant effort so we're... by zoul on Saturday February 03, 2018 @02:40PM (#16299153)

$250M sounds pretty behemotish?

[ Parent | on HN ]

Re:Slack: Other browsers require significant effort so we're... by ikonst on Sunday February 04, 2018 @02:56AM (#16301860)

Maybe not for the operation they're running, of which VoIP is only a small part.

[ Parent | on HN ]