@ryanflorence 1. node/AMD are two totally different semantics -- es6 modules fairly close to AMD semantics.
-
-
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 so is one of the constraints "AMD users must be able to get a transpiled ES6 module's default w/o .default"? Why?1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@ryanflorence Honestly I think it is. I think this layer of indirection is going to confuse people who currently use AMD3 replies 0 retweets 0 likes -
Replying to @kpdecker
@kpdecker@ryanflorence so the constraint is "the new system cannot confuse any consumers of any existing module system"?1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@ryanflorence If you want to use them in those module systems yes, I think.2 replies 0 retweets 0 likes
@kpdecker @ryanflorence existing AMD consumers have to know abt named exports. Saying "use the export named .default" shouldn't confuse
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.