how do you predict execution time? Just predicting whether preparse could be beneficial is already close to impossible
-
-
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 -
fascinating. Can you elaborate?
1 reply 0 retweets 1 like -
That was in the context of Angular 4.
1 reply 0 retweets 2 likes -
shipping 1000xdocument.createElement('tr') is cheaper than a 1000 line table. And you need the template anyw.
1 reply 1 retweet 3 likes -
Replying to @martin_probst @bmeurer
: this is very edge-casey, although I would use <iron-list> in many places to defer data loading
1 reply 0 retweets 0 likes -
: but with large tables (and other markup) we can progressively render, so not 1:1
1 reply 0 retweets 0 likes -
yeah, streaming ftw
1 reply 0 retweets 0 likes
: specifically, it lets the document remain interactive. Most FWs don't today: https://aerotwist.com/blog/when-everything-is-important-nothing-is/ …
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.