Modules: execute deps, modify, execute (was Re: ES Modules: suggestions for improvement)

[Jussi Kalliokoski]

This brings up an interesting point about the modules, that being lazy
loading. One appealing reason to use a module loader instead of just
concatenating the scripts or using multiple script tags is that you can do
feature detection and load polyfills for things you need instead of just
forcing the client to download all the polyfills, regardless of whether
they need them or not. Does the modules proposal attempt to solve this in
any way?

Cheers,
Jussi

On Wed, Jun 27, 2012 at 9:34 PM, John J Barton
<johnjbarton at johnjbarton.com>wrote:

>
>
> On Wed, Jun 27, 2012 at 9:47 AM, James Burke <jrburke at gmail.com> wrote:
>
>
>> The discussion on what is allowed, in particular import *, could still
>> happen, but at least there would be a baseline that would allow for
>> them in a way that makes it easier for existing code to transition to
>> the new world.
>
>
> I hope for a min/max module proposal to replicate the progress that the
> min/max class proposal produced.
> jjb
>
> _______________________________________________
> 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/20120627/5f52ee99/attachment.html>