- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Jul 2018 14:47:20 +0000
- To: public-webrtc-logs@w3.org
Short-term I'd suggest waiting until @henbos shipped transceivers in Chrome. The transceiver-transition in Firefox 59 went surprisingly smooth so I don't expect anything big to break even with addTrack. I hope he is writing tests in Firefox and running them in Chrome only when they are done :-) On a larger scale lets look at numbers for the addTrack adoption... from Chrome which shipped replaceTrack in M64 end of january 2018: https://www.chromestatus.com/metrics/feature/timeline/popularity/1641 -- shows addStream usage https://www.chromestatus.com/metrics/feature/timeline/popularity/2254 -- shows addTrack usage addStream is currently used on 0.04% of page loads, addTrack roughly 0.0025. That means addStream is used 16x as often as addTrack -- an adoption rate of 6.25%. We see some adoption in February and March and then even more adoption in with M65 mid-march. Note that we decided to bump the native addTrack to M65 in adapter which I think we can see here. What is odd about the addTrack numbers is that they show a very strong weekday/weekend cycle which is remarkably similar to the appear.in usage... This suggests that developers don't care about addTrack much. This adoption rate is after shimming addTrack in adapter and updating https://github.com/webrtc/samples to use it. I don't think we can repeat this for addTransceiver which will have a slow adoption rate starting at 0. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1758#issuecomment-404196634 using your GitHub account
Received on Wednesday, 11 July 2018 14:47:28 UTC