11–20 of 107 posts
At last. Where have they been all this time, under a rock? Does it mean they'll start supporting Opus as well?
Apple need to move Safari to the App Store. A Browser only being updated with the OS in 2016 is ridiculous.
From what I've been told, they are looking to hire 1 engineer. I guess that is better than nothing, but it doesn't look like webrtc is going to be any sort of priority for them. Also, it may not be super valuable in Safari, which has a small market-share. Where it is needed is mobile safari. From what I understand having it in Safari does not mean it gets built into mobile Safari. Also, note the date of the posting.…
At last. Where have they been all this time, under a rock? Does it mean they'll start supporting Opus as well?
Update:
It looks like Google Chrome (desktop) team has published a plugin that alleviates the problem but can cause performance degradations with apps that use WebRTC. They seem to suggest that a decent fix won't be possible until UDP proxies are in wide use and Chrome adds support for that.
Earlier quoted context omitted.
Apple need to move Safari to the App Store. A Browser only being updated with the OS in 2016 is ridiculous.
When you get 80%+ of your OS updated within 6 months this isn't so much of a problem.
From what I've been told, they are looking to hire 1 engineer. I guess that is better than nothing, but it doesn't look like webrtc is going to be any sort of priority for them. Also, it may not be super valuable in Safari, which has a small market-share. Where it is needed is mobile safari. From what I understand having it in Safari does not mean it gets built into mobile Safari. Also, note the date of the posting.…
iOS Safari has a large marketshare. WebRTC is more than video conferencing. It's also peer to peer networking which is a huge win for certain kinds of apps
Earlier quoted context omitted.
My guess is they didn't want to implement a competitor to FaceTime.
I wonder if there could be anything more toxic to a product's development than letting it compete.
How about the security issue with WebRTC where the browser leaks the IP address? It's part of the way WebRTC works so I can't see how that can be fixed. It's both a security issue and a key enabling feature. Update: It looks like Google Chrome (desktop) team has published a plugin that alleviates the problem but can cause performance degradations with apps that use WebRTC. They seem to suggest that a decent fix won't…