Why do es6 modules have to make up new semantics when AMD/node already have good ones?
@ryanflorence it would help if you could write up the constraints you are working within. There are many implicit ones in your statement.
-
-
@wycats@ryanflorence to me the biggest constraint is user knowledge. Loaders need to look for default or manual require('foo').default -
@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? -
@wycats@ryanflorence Honestly I think it is. I think this layer of indirection is going to confuse people who currently use AMD -
@kpdecker@ryanflorence "when transpiled and used with the old system" -
@wycats@ryanflorence yes. I have some concerns about the module vs. import syntax but those are minor relative to the transpile issue. -
@kpdecker@ryanflorence people will learn. -
@wycats@ryanflorence eventually yes given enough adoption of es6 modules but until that critical mass there will be pains. -
@kpdecker@ryanflorence I'm not clear why documenting that the interface for some module is .default will still be confusing
End of conversation
New conversation -
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.