Modularity: ES6 modules vs. HTML imports vs. asm.js
wycats at gmail.com
Sat Jun 8 17:35:04 PDT 2013
I started a conversation with Rafael Weinstein last week about the
possibility of integrating these systems. I believe that it is possible and
desirable, but there are many open questions to answer still.
It will be easier to begin the discussion seriously once the Loader API is
entirely specified, imho.
On Sat, Jun 8, 2013 at 7:33 AM, Sam Tobin-Hochstadt <samth at ccs.neu.edu>wrote:
> HTML imports are importing HTML, not JS. Coordination is always good,
> but I don't know what that would entail here.
> asm.js modules have some specific needs, and it may or may not be able
> to use ES6 modules. I'll let Dave speak to that.
> On Sat, Jun 8, 2013 at 9:56 AM, Axel Rauschmayer <axel at rauschma.de> wrote:
> > With Web Components, we also get HTML Imports . This seems like yet
> > another modularity construct on the web. Would it make sense to
> > this with ES6 modules? I’m also hoping/assuming that asm.js will
> > use ES6 modules(?)
> >  http://www.w3.org/TR/2013/WD-html-imports-20130514/
> > --
> > Dr. Axel Rauschmayer
> > axel at rauschma.de
> > home: rauschma.de
> > twitter: twitter.com/rauschma
> > blog: 2ality.com
> > _______________________________________________
> > es-discuss mailing list
> > es-discuss at mozilla.org
> > https://mail.mozilla.org/listinfo/es-discuss
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss