@csuwildcat @ebidel : the perf argument IS one if you need to parallelize requests and do de-dupe.
-
-
Replying to @slightlylate
@slightlylate@ebidel wait, wait, are you saying ES modules don't do similar diff/cache/dup resolution? If so, that wasn't my understanding.1 reply 0 retweets 1 like -
Replying to @csuwildcat
@csuwildcat@slightlylate@ebidel I would like to know this as well please1 reply 0 retweets 0 likes -
Replying to @eisaksen
@eisaksen@csuwildcat@ebidel : ES 6 modules are always later out of the gate (JS parser vs. HTML parser). Can parallelize thanks to syntax.1 reply 0 retweets 0 likes -
Replying to @slightlylate
@eisaksen@csuwildcat@ebidel : but you have other problems; notably you can't start to exec until you have all JS deps. Slower.1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@eisaksen@ebidel even so, probably wouldn't have anything in production but a flat JS module with CSS and asset includes.3 replies 0 retweets 0 likes -
Replying to @csuwildcat
@csuwildcat : you misunderstand the problem: vulcanize lets the browser chew on contents sooner. /cc@eisaksen@ebidel1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@eisaksen@ebidel that's precisely why you'd have a flat module without nested imports. You can exec that almost immediately.2 replies 0 retweets 0 likes -
Replying to @csuwildcat
@csuwildcat : these content types have different parsing behavior. It MATTERS. /cc@eisaksen@ebidel1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@eisaksen@ebidel obv diff content is parsed differently, I'd love to see real world perf of a flat JS module vs a flat Import1 reply 0 retweets 0 likes
@csuwildcat @eisaksen @ebidel : it's easy to reason about: serializing on JS parse or not.
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.