- From: Eric Rescorla <ekr@rtfm.com>
- Date: Tue, 4 Jun 2013 08:57:54 -0700
- To: cowwoc <cowwoc@bbs.darktech.org>
- Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
Received on Tuesday, 4 June 2013 15:59:05 UTC
On Tue, Jun 4, 2013 at 8:39 AM, cowwoc <cowwoc@bbs.darktech.org> wrote: > As an end-user, using DOM Futures was as simple as including the > Polyfill JS. Thing is, if WebRTC is built into the browser, I'm guessing > users would expect all dependencies (i.e. DOM Futures) to be built-in too. > > Seeing as the polyfill JS is rather small. What prevents you vendors > from folding this into the browser at the same time as WebRTC > Conversely, what prevents anyone who wishes to use a futures interface from loading their own WebRTC Futures wrapper? -Ekr
Received on Tuesday, 4 June 2013 15:59:05 UTC