@tomdale 1) it's a fact 2) incredibly arrogant to not consider that system and then expect it to support a new standard
-
-
Replying to @mikeal
@mikeal@tomdale the node.js module system was by far the dominant influence on the standard: http://jsmodules.io/1 reply 0 retweets 3 likes -
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
@mikeal also, @caridy maintains a ton of npm packages (https://www.npmjs.com/~caridy ) and @littlecalculist maintains the bindings to Rust (neon)
9:08 PM - 27 Apr 2016
1 reply
0 retweets
1 like
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.