- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 Jan 2025 08:38:07 +0000
- To: public-webrtc-logs@w3.org
> I think we need to distinguish theoretical differences from ones that matter. My bar for the shim was to minimize refactoring, not design a zero-work drop-in. > > All examples presented so far (here and in #116) stop both the original track and the processed track on main thread at the same time, so shimming `stop()` hardly seems necessary. One of the claims here is that the proposed change is not necessary because it is a "subset" that can be shimmed. It is good that we have now established that this claim is false. The rest of the arguments don't address the fact that many applications prefer to have the track on Window, since that is how tracks have always worked and provides for a better application architecture in many (probably most) cases. The argument that it is possible to write the application when the track is in the worker simply does not address this issue. -- GitHub Notification of comment by guidou Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/113#issuecomment-2586495565 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 January 2025 08:38:08 UTC