- From: Sean DuBois via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 May 2020 19:42:44 +0000
- To: public-webrtc-logs@w3.org
> if you're going to delay initial connection by 1 second, do it anywhere else People are going to abuse the API, most times accidentally. I am just trying to demonstrate where the API is needlessly fragile. This feels like 'Undefined Behavior' conversations. You can tell developers `Do not do that`, but they are going to do it anyway. Why not design the API to be robust. You can chase help people on SO every time this comes up, but why not fix the root cause? ----- I think we will just have to agree to disagree. Since I don't have W3C membership the conversations ends here, I appreciate you taking your time to discuss it though! Thank you for all your hard work on the webrtc-pc API :) -- GitHub Notification of comment by Sean-Der Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2519#issuecomment-623666100 using your GitHub account
Received on Monday, 4 May 2020 19:42:45 UTC