[whatwg] onclose events for MessagePort
dbk at google.com
Thu Oct 10 10:14:59 PDT 2013
On GC being a source of cross-browser difficulty: I think you can fix that
by stating in the messageport spec when we guarantee to implicitly close
the connection (when its host page closes) and when we provide no
guarantees (when it loses all its references).
On people relying on GC timing: Those people are being silly and deserve
what they get, as they do in Java. Using destructors in that language is
very nearly always a bad idea, but they still put them there and it was
I guess I think people who misinterpret the spec and do things which are
obviously a bad idea are only to a limited extent our problem. The web
needs to become a place where serious, large applications can be written,
it's not going to get there if the standard we set ourselves for the APIs
is "they can't possibly misuse this even if they've read no documentation
and are just guessing".
On Thu Oct 10 2013 at 1:00:54 PM, Boris Zbarsky <bzbarsky at mit.edu> wrote:
> On 10/10/13 11:43 AM, David Barrett-Kahn wrote:
> > Why is revealing when garbage collection happens such a terrible thing
> > anyway?
> Because web pages can then start depending on GC timing, limiting the
> kinds of GC optimizations browsers can do.
More information about the whatwg