I believe Node.js leadership is not qualified to make the .mjs decision. Let the community vote with what they use!https://twitter.com/wycats/status/736972528942383104 …
-
-
Replying to @ebryn
@megalithic@wycats in related news, maybe read https://medium.com/@bradleymeck/understanding-the-hard-choice-1ea3008fc9d0#.nsuuxj4ds …1 reply 0 retweets 0 likes -
Replying to @Fishrock123 @ebryn and
also I am happy to answer any questions about it (and please ask them)
1 reply 0 retweets 0 likes -
I have read this. I didn't feel it addressed all of the concerns in a new way.
1 reply 0 retweets 0 likes -
Replying to @wycats @Fishrock123 and
more directly: what's the rush? Why does it HAVE to land in node7?
1 reply 0 retweets 0 likes -
It doesn’t have to. That is an option we have kept open. We have only said we would probably implement it a way.
2 replies 0 retweets 1 like -
Replying to @Fishrock123 @ebryn
count me as one in favor of holding off on modules in node7 so things can settle and give us time to do it right
1 reply 0 retweets 1 like -
Replying to @wycats
we can’t implement them in node 7 or probably 8 anyways, loader impls, vm parsing support etc, isn’t nearly there.
1 reply 1 retweet 0 likes
interesting -- I thought all of this was about node7!
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.