Comment by wbobeirne
20 hours ago
Running a performance profile in Chrome doesn't back this up for me, and looking at the loop it looks like it maintains an active `Set<JellyComponent>()` of which components to update, and clears them out when they stop moving.
Agreed the comments look a bit slop-ish but I don't see anything obviously wrong with its approach, and the core loop is running in microseconds for me when nothing is happening.
Here's the perf profile, just to clarify.
Cursor idle, viewport on the button examples. 3ms repaint every 8-11ms. Animation frame points to the code i mentioned.
https://postimg.cc/sQpZxxzv
The problem isn't doing work on a website, its if you have an idle task that is taking up a significant portion of the frame budget then its easy to have frame drops when you do significant work like clicking, scrolling, browsing.
Idle work showing up in flamecharts is usually the thing to be cautious of.
That's from Lottie, the animations that play in the header and footer of the page. Shrink your window until they disappear and try again.
Oh, yea, "you're holding it wrong"
1 reply →
Is it? I am in the middle of the page, the header and footer are well off into the distance not being rendered, and I see the same pattern.
https://imgur.com/texxYP0
1 reply →