> I guess I don't see a reason why you can't do all of that with
subclassing.  The only thing subclassing is going to force you into is
using the system's microtask queue.  Other than that you can tweak the API
all you like.  It's hard to believe that a user-land library can beat the
system in terms of performance and debug-ability.

Okay, lets say that this is indeed would be the ideal way to go about it.
I'm far from convinced (interfaces, not subclassing is the solution here --
but not too broad of an interface), but lets just leave that aside - the
fact is, I am not an implementer, Petka Antonov would know the right answer
to that question.

My understanding is that its too late for that proposal, right? It has been
already decided that backwards-compatibility is important. I believe you
also mentioned that its "probably too late". Well, its still not too late
for ghetto anti-branding. It doesn't noticeably change exiting behavior -
its backwards-compatible, yet provides an "exit" for the future.

Can you leave what you feel is the best solution aside for a moment and
comment on this proposal instead?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20131221/5ef0aa38/attachment.html>

> I guess I don't see a reason why you can't do all of that with subclassing.  The only thing subclassing is going to force you into is using the system's microtask queue.  Other than that you can tweak the API all you like.  It's hard to believe that a user-land library can beat the system in terms of performance and debug-ability.

Okay, lets say that this is indeed would be the ideal way to go about it.
I'm far from convinced (interfaces, not subclassing is the solution here --
but not too broad of an interface), but lets just leave that aside - the
fact is, I am not an implementer, Petka Antonov would know the right answer
to that question.

My understanding is that its too late for that proposal, right? It has been
already decided that backwards-compatibility is important. I believe you
also mentioned that its "probably too late". Well, its still not too late
for ghetto anti-branding. It doesn't noticeably change exiting behavior -
its backwards-compatible, yet provides an "exit" for the future.

Can you leave what you feel is the best solution aside for a moment and
comment on this proposal instead?