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.
-
Show this thread
-
Replying to @AbolitionOf
The process used to ratify ESM is no longer the process. Even by current TC39 standards this was a mistake.
1 reply 0 retweets 12 likes -
Replying to @mikeal @AbolitionOf
TC39 is ground-zero for a lot of process meta-argument, but this is a pretty bad entry to that pantheon. Sync `require()` was never going to fly on the client, nor were extra lookups for indexes. We learned a(and walked back) these mistakes in '04-'08. Why repeat?
3 replies 0 retweets 11 likes -
Replying to @slightlylate @AbolitionOf
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.
1 reply 0 retweets 1 like -
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."4 replies 0 retweets 16 likes -
fwiw this is also my experience as a p fly guy during that period
1 reply 0 retweets 3 likes
...for a white guy?
-
-
Replying to @slightlylate @tomdale and
don't try to put me in a box alex
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.