Saying the payload may be a bit bloated at times misses the forest for the trees.
-
-
Replying to @AdamRackis
: not just talking about webdev. We see the same thing w/ folks showing up w/ server-side C++ chops and flailing. Client is hard.
2 replies 1 retweet 3 likes -
Replying to @slightlylate
: on server, your static initializers might hurt your app startup a bit, but how often do they start? On client, can be critical.
1 reply 0 retweets 1 like -
Replying to @slightlylate
: e.g., at some point in '09 we went on a rampage to eliminate all SI's because they tanked Chrome startup. Massive win.
1 reply 0 retweets 1 like -
Replying to @slightlylate
: similarly, who cares how many .so's (or DLLs) your thing is made of on the server? On the client, that's seek-time & YOU LOSE.
1 reply 0 retweets 1 like -
Replying to @slightlylate
: but the key in both cases was doing what the JS community seems not to do much today: respecting low-end hardware's limits.
4 replies 0 retweets 2 likes -
Replying to @slightlylate
Payload size & time to render on old phones is only 1 metric among many that'll govern architecture decisions.
1 reply 0 retweets 1 like -
Replying to @AdamRackis
: we're all optimizing against a hierarchy of constraints. The order matters & defines many outcomes.
1 reply 0 retweets 1 like -
Replying to @slightlylate
I also worry about optimizing for "where the puck is, vs where it's heading" Will slow today on old phone still be so in 6mo?
2 replies 0 retweets 0 likes -
: the reason here is that network latency & real CPU gains aren't what the marketing suggests it will be.
-
-
Replying to @slightlylate
: e.g. if you look at marketing, you see core counts...but how long can they run full throttle w/o thermal throttling? (not long)
1 reply 0 retweets 0 likes -
Replying to @slightlylate
: sorry, no, I'm talking about the mid-priced phone in *wealthy* markets. Frequently thermally throttled.
0 replies 0 retweets 1 like
End of conversation
New conversation -
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.