> On Jun 20, 2014 11:39 AM, "John Barton" <johnjbarton at google.com> wrote:
> > I started out with a similar opinion. Then I wrote some ES6 code.
> >
> > What we need now is experience from using ES6-modules. We have plenty
of decent implementations. We've built nodejs and browser applications
based on ES6 modules. That experience shows that the ES6 solution is
modestly superior to any ES5 solution. Moreover the ES6 solution
interoperates with the main ES5 solutions.  Are there projects which
attempted to use ES6 modules but where unable to succeed because of
technical barriers?

It would certainly be helpful if there was a migration doc written that
carefully explained the "best practices" way to allow your node
package/script-tag library/amd module/commonjs module to support ES6
modules as well, in the spirit of the one-liner "amd or node.js or..."
prefixes that are commonly used.
  --scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140620/a92737a3/attachment.html>

> Are there projects which attempted to use ES6 modules but where unable to succeed because of technical barriers?

It would certainly be helpful if there was a migration doc written that
carefully explained the "best practices" way to allow your node
package/script-tag library/amd module/commonjs module to support ES6
modules as well, in the spirit of the one-liner "amd or node.js or..."
prefixes that are commonly used.