- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Sun, 15 May 2022 17:26:55 +0000
- To: public-webrtc-logs@w3.org
> [By @jan-ivar] I'm not ignoring your arguments, I felt @youennf [dismantled them sufficiently](https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1064903263) much better than I could, and saw no need to pile on. @jan-ivar, this message is outright false. * First, our correspondence on "priority of constituencies" happened on February 3. You completely ignored my argument and proceeded with other topics, still on February 3. The message by Youenn which you [reference](https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1064903263) was posted on March 11 - more than a month later. [*] * Second, the [message](https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1064903263) by Youenn's which you [reference](https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1126846959) did not even deal with "priority of constituencies". It dealt with the implementability of alternative approaches. [*] * Third, you have since brought up "priority of constituencies" [multiple additional times](https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1126813025). I countered each time, and you ignored my counter-arguments each time. Could you please reply to the arguments rather than act as if they don't exist? Namely - what cost do users and developer incur, if the API is made asynchronous? -- [*] Noteworthy: Youenn did post [an earlier message](https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1029789637) on February 4, addressing "priority of constituencies". It reiterated Youenn's conclusion with no supporting arguments, claiming an asynchronous API "is more costly to both web developers and web engines" without explanation. It certainly did not "dismantle" any arguments, or even acknowledge any. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1126982932 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 15 May 2022 17:26:56 UTC