Bradley Meck bradley.meck at
Tue Aug 18 22:05:33 UTC 2015

The problem is timing; WHATWG uses promises, which Node cannot use due to
existing code bases on npm + potential mixing w/ `require`. This causes
time discrepancies and would mean different actions depending on how
exactly hooks are specced out. Node does not want to prevent async loading
on the browser, and the WHATWG loader does not want to cause breakage in

On Tue, Aug 18, 2015 at 4:56 PM, Jason Orendorff <jason.orendorff at>

> On Tue, Aug 18, 2015 at 12:45 PM, Bradley Meck <bradley.meck at>
> wrote:
> > This would assume they can support the transformation hooks to do things
> > like load coffeescript etc. right now, which is the main contention
> point.
> It is a perfectly ordinary occurrence in software to ship some
> capability at one point, and ways of customizing that capability
> later.
> -j
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list