Drafting a solution for ES imports that avoids `.mjs` or other signals.
Step 1: Lock @BrendanEich & @isntitvacant in a room.
Step 2: Wait.
-
-
Replying to @jmar777
BrendanEich Retweeted BrendanEich
Not transparent. See https://twitter.com/brendaneich/status/726210844296515584 …. Node.js cheated on async-always by making require block in kernel. Filesystems slow.
BrendanEich added,
4 replies 1 retweet 2 likes -
Replying to @BrendanEich @jmar777
IIRC very early Node had async require, too painful - yet that would've muxed I/O better, & been compatible w/ browser requirement.
1 reply 0 retweets 3 likes -
Replying to @BrendanEich
.
@jmar777 Should anyone say async require "is on Node" to agree to? Of course not. So don't say or imply that blocking require is "on TC39".2 replies 0 retweets 2 likes -
Replying to @BrendanEich @jmar777
The sync require from filesystem cheat was the right hack for usability. But it *pre-diverged* from standardizable modules in ES6.
3 replies 0 retweets 6 likes
"pre-diverged from a standard" is a weird turn of phrase, no?
-
-
It's intentionally Math-y, but not pejorative. We knew in 2010 we couldn't do blocking require in ES6; too late even then.
0 replies 0 retweets 2 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.