@mikeal @tomdale the node.js module system was by far the dominant influence on the standard: http://jsmodules.io/
-
-
Replying to @wycats
@mikeal@tomdale early on,@izs wrote a great post about this and we read it carefully. Current status:http://blog.izs.me/post/25906678790/on-es-6-modules …1 reply 0 retweets 2 likes -
Replying to @mikeal
@mikeal@tomdale Compatibility with Node.js was a requirement from the get-go. I talk about it here: https://gist.github.com/wycats/51c96e3adcdb3a68cbc3 … (March 2013)1 reply 0 retweets 1 like -
Replying to @wycats
@mikeal also,@caridy maintains a ton of npm packages (https://www.npmjs.com/~caridy ) and@littlecalculist maintains the bindings to Rust (neon)1 reply 0 retweets 1 like
@mikeal all of us are heavy users & contributors to the node ecosystem & also early adopters of standard modules. We engage because we care.
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.