Right, I think this is a case of efficiency vs fidelity. IO is efficient, CW is high fidelity.
sounds like IO isn't firing enough based on actual real-world tradeoffs. @slightlylate this should be fixed
-
-
… BUT I think, looking at the spec, if you want per-frame updates about scroll, you want CWs.
-
you don't want per-frame updates. you want "as much as possible while avoiding jank"
-
guaranteed per-frame updates are just too big of a sledge-hammer here.
End of conversation
New conversation -
-
-
I think we need data either way as to how often it fires under heavy load etc.
-
: srsly, you could be testing IO instead of tweeting about perceived "issues"
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.