Doing it 30x more frequent than needed costs more, no matter if it's only 1 pixel.
This problem is not isolated to me or to just one machine. Check out the chromium bug about the tab loading spinner, for example. It is a "simple" spinner as well.
Or the Zed editor, which spams screen redraws even when nothing changes at all, so it has high GPU usage for still picture.
I'm sure that some spinners are horrible and peg the CPU, but unless your machine is older than ~2018 there is something wrong with your setup if spinners (and not intense operations behind them) cause your battery to suffer.
Opening https://nh2.me/low-fps-spinners/smooth-spinner.html it doesn't matter if I zoom the spinner to 25% or 500%: Despite the 400x difference in pixels redrawn, the "GPU Process" CPU usage in the "Browser" tab of the Chromium Shift+Esc task manager is equally high.
It only scales down the cost when reducing the FPS.
But do really have the CPU/GPU go idle, you need to not use them; the only solution to that is to show still images, aka reduce FPS.
Hah, I did not expect that. I can't imagine any end users will be able to name that one.
Anecdotally, I’ve only ever heard non-frontend developers call them “spinners”.
Maybe starting a discussion on the articles’ talk page could elicit some change? Language evolves, after all.
Such as these non-frontend devs?
https://learn.microsoft.com/en-us/previous-versions/windows/...
I think they fell out of fashion after the scroll wheel was invented
Low fps seems jerky/retro?
Does "Square ring" really look jerky/retro?