import script --> .esm

Matthew Robb matthewwrobb at
Wed Sep 10 11:28:11 PDT 2014

I don't see how this is not forking:

There are now two distinctly different models and yes they both work in the
same VM simultaneously but that's not what authors would care about.
Personally I want to be able to know at all times that a file I am looking
at is a script or a module without using tools to assume one or the other.

The problem with the link above is that A) It associates this new
local-global-scoping/implicit-strict-mode with modules rather than
generically and B) Neither mode is specified as of higher importance which
results in exactly a forked paradigm.

- Matthew Robb

On Wed, Sep 10, 2014 at 2:15 PM, Brendan Eich <brendan at> wrote:

> Matthew Robb wrote:
>> But if the goal is for everything going forward to use the scope
>> environment characteristics of modules (strict-mode and local-global) then
>> why not specify that and move the old model to a legacy mode.
> What "old model"? There's one spec. We are not forking specs. Engines are
> not forking into two VMs.
> /be
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list