IO is the right tradeoff of expressiveness and jank imo.
-
-
-
Replying to @aerotwist @wanderview and
the intent of IO is to give you enough callbacks to do what you need, but not too many.
1 reply 0 retweets 0 likes -
Replying to @wycats @aerotwist and
placeholder boxes are preferable to jank. if IO isn't firing enough, I'd say browser bug
1 reply 0 retweets 0 likes -
Replying to @wycats @aerotwist and
IO should be the general-purpose tradeoff, and browsers should handle the "it depends" issue
1 reply 0 retweets 1 like -
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
… BUT I think, looking at the spec, if you want per-frame updates about scroll, you want CWs.
1 reply 0 retweets 1 like
you don't want per-frame updates. you want "as much as possible while avoiding jank"
-
-
Replying to @wycats @aerotwist and
guaranteed per-frame updates are just too big of a sledge-hammer here.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.