SebastianVerified account

@mikeal It would almost be easier if it was one thing. This stuff is seriously going to hurt beginners though: http://logs.libuv.org/node-dev/2016-01-25#16:58:41.717 …

@Fishrock123 @mikeal I'm not sure I follow the problem – loader spec necessitates that module execution resolves as a promise?

@isntitvacant @mikeal it carelessly disregards the notion that there might be an existing module system

@Fishrock123 @mikeal what would be the problem with throwing the ES6 module's promise into the require.cache?

@isntitvacant @mikeal the semantics become very difficult to understand we want people who are not experts to use this stuff right?

@Fishrock123 @isntitvacant the question there isn't what the total complexity is but what is the minimum understanding you need to use it.

@mikeal @isntitvacant also, I don’t think core has (or will have) enough full time people to make sure all of ES6/7 can work in node

@Fishrock123 @isntitvacant the vast majority of ES6/7 is purely in the VM, stuff like modules that need to be integrated as the exception.