Those parsers look for resources to fetch (pre-parsing and scanning). When you bake that into script, you defeat that whole system.
-
-
Replying to @slightlylate
...which means the latency to begin fetching those resources is now much higher in the common case. Of course, you can work around (kinda)
1 reply 0 retweets 8 likes -
Replying to @slightlylate
A bigger toolchain, <link rel="prefetch">, H/2 push, etc. You can get some of it back, but not entirely.
1 reply 0 retweets 8 likes -
Replying to @slightlylate
But it's not just parsers! When you bake, e.g., CSS & templates into script, those things live in the heap. We can't drop them (usually).
2 replies 6 retweets 16 likes -
Replying to @slightlylate
So memory footprint goes up. The code that's generated is only a part of it; the source code stays around in most impls today -- often large
2 replies 1 retweet 9 likes -
Replying to @slightlylate
The larger issue, of course, is script eval is single-threaded. We can't construct (e.g.) DOM off-thread. And script ~10x slower on phones.
2 replies 2 retweets 13 likes -
Replying to @slightlylate
Not all phones, mind. Developers with ~$700 iPhones & Pixels are living in a different world to most folks.
2 replies 5 retweets 19 likes -
Replying to @slightlylate
unrelated, but pixel web scores are 1/3 iPhone 7's. Is this purely hardware or is software playing a significant role too?
1 reply 0 retweets 0 likes -
Replying to @danbucholtz
: a bit of both; depends on benchmark, but the HW differences are huge. Straight-line, singled threaded perf stresses caches.
1 reply 0 retweets 1 like -
Replying to @slightlylate
: something important here: iPhones have HUGE L2/3 caches (historically). Can't buy an equivalent Qualcomm part today.
2 replies 0 retweets 4 likes
: I have massive respect for Apple's HW. Amazing screens/digitizers, great thermal balance. This is an example of perf balance.
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.