SebastianVerified account

@mikeal @domenic @fishrock123 @isntitvacant yes. there's no solution where you aren't making massive compromises.

@mikeal @domenic @fishrock123 @isntitvacant if you want commonjs then use `require`, if you want es then use `import`. why is that bad?

@sebmck @mikeal @domenic @fishrock123 @isntitvacant what happens when you don’t know what the module is? i.e., something from npm?

@sebmck @mikeal @domenic @fishrock123 @isntitvacant unless it’s something like: npm -> use require(), your code -> use `import`

@miksago @sebmck @domenic @Fishrock123 @isntitvacant can someone explain what part of this is an actual improvement?

@mikeal @miksago @sebmck @domenic @fishrock123 it lets you use other new syntax w/o fear of circular deps, IIUC

@isntitvacant @mikeal @miksago @domenic @fishrock123 circular deps, live bindings, trivially statically analysable, asynchronous resolution

@sebmck @isntitvacant @mikeal @miksago @domenic @Fishrock123 async resolution is not demanded by spec (and tends to slow things)