Ignore for a moment that a spec exists for ESM and just look at the implementations. The JS modules story would be: * Node.js made a module system. * Webpack made a slightly better but 100% compatible module system. * Browsers made small adjustments to it that broke everyone.
-
-
I don’t think there was ever a serious argument made that the browser should adopt a synchronous lookup mechanism for modules. Nor was anyone in the actual Node.js project engaged enough with TC39 to make such an argument.
-
As a fly on the wall during that period:
@wycats and@littlecalculist considered Node/browser interop a top priority and tried (to the best of their abilities) to reach out. There was quite a bit of anti-TC39 sentiment at the time, and most feedback was "just use Node modules." - 7 more replies
New conversation -
-
-
I am yet to see any case that is covered by `import` that isn't covered by `require`, and plenty of the inverse.
-
This sort of misses the point: the price of a `fstat` on local disk is near-zero; the price of `fstat` in the critical path, over the network, is bonkers. The syntax and semantics hinge on this.
- 3 more replies
New conversation -
-
-
To your first point: you could personally have a lot of impact on improving that. You know what I mean and what I'm talking about.
-
I do. Have stayed my hand multiple times in hope chair changes improve things. Still looking closely.
End of conversation
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.