IO should be the general-purpose tradeoff, and browsers should handle the "it depends" issue
-
-
Replying to @wycats @wanderview and
you can’t get placeholder boxes recycled if you don’t know they’re needed; reqs per-frame update
2 replies 0 retweets 1 like -
Replying to @aerotwist @wanderview and
you can fill in as many future placeholders as you need based on the number of IO "misses"
1 reply 0 retweets 0 likes -
Replying to @wycats @wanderview and
that’s possible, though DOM node count goes up for a larger runway = increased jank likelihood
2 replies 0 retweets 0 likes -
sounds like IO isn't firing enough based on actual real-world tradeoffs.
@slightlylate this should be fixed2 replies 0 retweets 0 likes -
Replying to @wycats @wanderview and
I think we need data either way as to how often it fires under heavy load etc.
2 replies 0 retweets 0 likes -
Replying to @aerotwist @wanderview and
if the data is used to fix IO, sure. if it's used to justify mandatory hi-fi, no.
1 reply 0 retweets 0 likes -
Replying to @wycats @wanderview and
that would beg the question. I want to see what’s fit for which case.
1 reply 0 retweets 0 likes -
Replying to @aerotwist @wanderview and
you don't understand me. IO was designed asthe "it depends" killer. If "it depends" IO failed
1 reply 0 retweets 0 likes -
Replying to @wycats @wanderview and
Perhaps my world view, but when it comes to perf I’m more of a “do whatever works” type chap.
1 reply 0 retweets 0 likes
"whatever works" surely does not include features that have not yet shipped in any browser.
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.