Are ES6 modules in browsers going to get loaded level-by-level?

Matthew Robb matthewwrobb at gmail.com
Fri Apr 24 00:10:24 UTC 2015


It would be great if the web app manifest included the dependency graph for
the app. Something like the depCache in system js.
On Apr 23, 2015 8:03 PM, "Matthew Phillips" <matthew at bitovi.com> wrote:

> I think the issue of round-trips is a red-herring. I spent some effort
> trying to optimize an es6 loader with caching in indexeddb and even that
> did not help much.  I think what caridy said earlier is likely the biggest
> issue, processing a large number of Promises.
>
> On Thu, Apr 23, 2015 at 7:55 PM, John Barton <johnjbarton at google.com>
> wrote:
>
>> Sorry, but what I read was not an explanation but rather a hope that
>> HTTP/2 would magically solve this problem.  I'm all for HTTP/2 solving
>> this. But so far I've not heard or read anything to back up the idea.
>>
>> Will HTTP/2 make multiple round trips, one for each level of the
>> dependency tree, competitive with pre-bundling? If not, then we will have
>> to send dependency info to the client or cache info to the server or
>> bundle. Or there is some magic as yet unexplained?
>>
>> jjb
>>
>> On Thu, Apr 23, 2015 at 7:47 AM, Domenic Denicola <d at domenic.me> wrote:
>>
>>>  Indeed, there is no built-in facility for bundling since as explained
>>> in this thread that will actually slow down your performance, and there’s
>>> no desire to include an antipattern in the language.
>>>
>>>
>>>
>>> *From:* es-discuss [mailto:es-discuss-bounces at mozilla.org] *On Behalf
>>> Of *Eric B
>>> *Sent:* Thursday, April 23, 2015 10:25
>>> *To:* Frankie Bagnardi; Matthew Phillips
>>> *Cc:* es-discuss
>>> *Subject:* Re: Re: Are ES6 modules in browsers going to get loaded
>>> level-by-level?
>>>
>>>
>>>
>>> So just to clarify, when browsers support es6 modules we will still need
>>> some extra library to bundle the modules?  This would mean es6 modules are
>>> only a syntactical addition and not something functional?
>>>
>>>
>>>
>>> On Thu, Apr 23, 2015 at 10:18 AM Frankie Bagnardi <f.bagnardi at gmail.com>
>>> wrote:
>>>
>>>  Matthew, there are already tools for es6 modules + bundling (e.g.
>>> babel + webpack), or converting es6 modules to AMD (e.g. babel
>>> <https://babeljs.io/docs/usage/modules/>).
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Apr 22, 2015 at 7:10 PM, Matthew Phillips <matthew at bitovi.com>
>>> wrote:
>>>
>>>
>>>  Can you clarify what you mean about bundling? Unless I've missed
>>> something, the ES6 module system does not have a story for bundling at all.
>>> Of course formats can be invented in userland but I'm not sure that they
>>> are any easier to implement than say AMD's.  I might have missed something
>>> though, looking forward to your reply.
>>>
>>>
>>> _______________________________________________
>>> 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
>>> https://mail.mozilla.org/listinfo/es-discuss
>>>
>>>
>>> _______________________________________________
>>> es-discuss mailing list
>>> es-discuss at mozilla.org
>>> https://mail.mozilla.org/listinfo/es-discuss
>>>
>>>
>>
>
>
> --
> Bitovi
> Development | Design | Training | Open Source
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150423/fb6f6172/attachment.html>


More information about the es-discuss mailing list