Why do es6 modules have to make up new semantics when AMD/node already have good ones?
-
-
Replying to @ryanflorence
@ryanflorence 1. node/AMD are two totally different semantics -- es6 modules fairly close to AMD semantics.1 reply 1 retweet 1 like -
Replying to @ryanflorence
@ryanflorence@samth What are you talking about exactly? New semantics support cycles, default/named exports w/o collision with F.p/O.p1 reply 1 retweet 1 like -
Replying to @ryanflorence
@ryanflorence it would help if you could write up the constraints you are working within. There are many implicit ones in your statement.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@ryanflorence to me the biggest constraint is user knowledge. Loaders need to look for default or manual require('foo').default2 replies 0 retweets 0 likes -
Replying to @kpdecker
@kpdecker@ryanflorence why doesn't module.exports = default; default.default = default; mixin(default, exports)?2 replies 0 retweets 0 likes
@kpdecker @ryanflorence and blacklist named exports on O.p and F.p at compile-time
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.