@mikesherov @brianleroux iow Node already introduced the ambiguity and didn't feel the need to choose `.njs` or `.cjs` for Node.js modules
@bradleymeck @mikesherov @brianleroux Right now we use import 'npm:*' due to the primacy of standard modules, but working to eliminate 2/2
-
-
@wycats@mikesherov@brianleroux this looks like it is just transforming the source down to Script if I am reading it right? -
@bradleymeck@wycats@mikesherov waking up to this thread.
Time to reboot the spec for sure! NBD. Happens. -
@brianleroux@wycats@mikesherov Problem was TC39 said "we know best", didn't invite others in.@bradleymeck and@jrburke should have been. -
@brianleroux@wycats@mikesherov@bradleymeck So now we see the repercussions of an uncollaborative spec. -
@matthewcp --@littlecalculist exchanged pages and pages of emails and in-person chats with@jrburke ;@othiym23 attended TC39 meetings 1/ -
@matthewcp@littlecalculist --@othiym23 and others were always welcome. Responses to https://gist.github.com/wycats/51c96e3adcdb3a68cbc3 … drove the spec 2/ -
@matthewcp@littlecalculist -- we paid a lot of attention to@izs' blog post (http://blog.izs.me/post/25906678790/on-es-6-modules …) 3/ -
@matthewcp "The current ES6 Module specification has changed a lot since then, and many of my complaints have been addressed" 4/ - 3 more replies
New conversation -
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.