- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Jan 2025 09:13:14 +0000
- To: public-webrtc-logs@w3.org
> The API currently in the spec (with a lot of "no consensus" remarks that make it impossible to move that API to PR) is a proposal. It is more than a proposal. The API reached consensus within the WebRTC WG 3 years ago and the API has received very few API updates during those 3 years. Since then, the API has been validated by implementation and shipped. > the API currently in the spec may not be the best for developers. The bar is pretty high to do a full redesign, given what I mentioned above. The summary of the discussion AIUI is: - There is no loss of functionality when using the standard API. - There may be performance issues with the standard API, it is still unclear where and how much. - There is some amount of work to do the transition from the proprietaty API to the standard API. The main issue seems to lie around `applyConstraints`. `stop` and `enabled` have been mentioned by @guidou as well. It is not clear what this amount of work is and whether it is unreasonable. @jan-ivar showed a small but partial shim. - This amount of code may deter existing apps from using that API (these apps may stick to `rvfc` and friends). -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/113#issuecomment-2589389405 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 January 2025 09:13:15 UTC