- From: Richard Barnes <rbarnes@mozilla.com>
- Date: Wed, 12 Feb 2014 19:44:53 -0500
- To: Jonas Sicking <jonas@sicking.cc>, Boris Zbarsky <bzbarsky@mit.edu>
- CC: Ian Hickson <ian@hixie.ch>, Arvind Jain <arvind@google.com>, public-web-perf <public-web-perf@w3.org>
On 2/12/14, 6:33 PM, Jonas Sicking wrote: > On Wed, Feb 12, 2014 at 3:02 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: >> On 2/12/14 5:52 PM, Jonas Sicking wrote: >>> >>> I personally think C makes the most sense since it doesn't involve >>> grabbing some omnious global state. Instead the behavior is determined >>> by the more tangible answer to the question "which object did you call >>> a function on". >> >> What object, or what function? >> >> Consider windowC.navigator.sendBeacon.apply(windowD.navigator, args) > > I would say D here. Carrying state in functions feels a lot more hacky > than carrying state in objects. That was my reaction as well. --Richard > > / Jonas >
Received on Thursday, 13 February 2014 00:45:16 UTC