Re: [mediacapture-transform] We shouldn't require track transferability (#113)

> > That there are two implementations doesn't prevent changing the spec to improve it
> 
> What is proposed is an entire rewriting the API/WebIDL, which means rewriting a large part of the spec.
> 
Nothing of the sort. The proposal is basically adding a new factory method  for MSTP /VTG. No need to remove anything


> > The use case for managing the track on Window is all existing applications.
> 
> It would help immensely if we have a solid proof that the new API is hard to use. So far, it does not seem to be the case.
> 

Safari implements it. Are you aware of any major applications moving from canvas capture to the new API? Can you share any adoption numbers?
Maybe we can also conduct some sort of developer survey.

> AIUI, the current API and the proposed API have the same feature set, so there should be no impact on end users. All we are debating is ease of use of the two APIs.
> 
The proposed API is just an additional factory method so that you xan keep the tracks on Window, which will make it easier to migrate existing applications and develop new ones following commonly used patterns withvMediaStreamTracks

> We should compare this potential ease-of-use benefit with the known amount of work building the new proposal would require:
> 
> 1. WebRTC WG discussions to reaching consensus on the new API design
> 2. Rewriting of the spec
> 3. Deprecation and removal of the current API (we surely do not want to have two APIs for the same job)
> 4. Reimplementations in all browsers.
> 
> This is a big ask.

The needs of users and Web developers are above the needs of browser implementers and spec writers in the priority of constituencies so I don't see this as a blocker.
Also, in terms of implementation, the proposal reuses a pattern already implemented in browsers for encoded transform.




-- 
GitHub Notification of comment by guidou
Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/113#issuecomment-2536722288 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 11 December 2024 18:03:23 UTC