Rationale for dropping ModuleImport syntax?

Kevin Smith zenparsing at gmail.com
Thu Jun 12 12:50:57 PDT 2014

> I was more wondering if there was anything preventing a module import
> statement from being added later, if it was found to be a requirement.
> I can't see any reason why it couldn't, that would also allow time for
> bikeshedding the syntax.

It could be added later, but to turn the question around:  why should it be
dropped?  It has been part of the design for a very long time, it's
currently used by many people working in the ES6 space, and it meets a
semantic need.

If you want to drop a feature this late in the game, then you need to show
that it's one of the following:

1. Buggy
2. A footgun
3. Not useful
4. Future-hostile

I don't see that it meets any of those requirements, do you?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140612/4c9a220f/attachment.html>

More information about the es-discuss mailing list