the only thing i get from both threads is how they manage to take WebGL instanced rendering and make it slow, in two different ways...
-
-
-
IKR? The original thread is talking about how "impossible" it is to update 2K components...on desktop class hardware...in 2019. Surely there's a limit to "worse" in "worse is better"?
- 4 more replies
New conversation -
-
-
-
Except we already did in Vue 3.
- 3 more replies
New conversation -
-
-
My big takeaway with react scheduler example was that it replaced one kind of bad with another. The webgl ball is clearly the whole point of that app, making it choppy so the UI is responsive is marginally better I guess but still bad.
-
I mean if this is the pinnacle of good UX, I don’t really know what to say.
- 8 more replies
New conversation -
-
-
To be fair this demo wasn't from the react team, who used data fetching as the show case for the schedular. Latency across the net is what they were mitigating.
-
And besides they are using a browser api in requestIdleCallback that is designed to allow for exactly such things
End of conversation
New conversation -
-
-
Is it elitism if I advocate for for loops and arrays? If you take libraries whose trick is to avoid unnecessary work and changes, and then force changes, you are only left with the overhead.
Thanks. 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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.