eval === preparse and/or parse and/or execute?
-
-
-
Replying to @slightlylate
how do you predict execution time? Just predicting whether preparse could be beneficial is already close to impossible
2 replies 0 retweets 0 likes -
Replying to @bmeurer
: I suspect we could do decent baseline + local learning. Basically, tho, refuse more than ~350k of JS (gzipped) w/o user consent
1 reply 0 retweets 1 like -
Replying to @slightlylate
That doesn't sound like a good heuristic to me. 350k of JS can be fairly cheap to (pre)parse and execute.
1 reply 1 retweet 4 likes -
Replying to @bmeurer @slightlylate
Actually just had a long chat with
@martin_probst today that sending rendering commands as JS can be way cheaper than HTML.2 replies 0 retweets 7 likes -
That being said, I think there's a lot of nuance here.
2 replies 0 retweets 0 likes -
Replying to @bmeurer
: most mobile scenarios I trace have JS, and lots of it, in the critical path. Need ways to cut that down.
1 reply 0 retweets 3 likes -
Replying to @slightlylate
Right. I think we need to find ways to quantify and communicate that. JS in critical path can still beat HTML+CSS sometimes
2 replies 1 retweet 4 likes -
Replying to @bmeurer @slightlylate
It's not black and white. And oftentimes V8 is to blame too, which was/is our own fault. I did a bit of that for sure.
2 replies 1 retweet 1 like
: agree not B&W, but shifting the environment requires bright, enforceable lines
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.