The issue is from early April and still open lol
“Coding is solved”
Instead of spinners, you should use progress bars. When the endpoint of a process is unknown, you should just have a ticker that displays an increasing number. In codex, for example, just show me the number of tokens read or generated so far. It gives me feedback that the process hasn’t frozen, and it provides useful information. What an easy and cheap solution!
Was the animation vibe coded by any chance?
Not vibecoded, completely vibed:
while(working) { chatgpt.prompt("Please generate an image similar to the current spinner image, but rotated a slight bit more to the right."); }Their fix will probably be, adding “Give a quick answer, don’t think too hard” to the prompt.
We should go back to the 8 frame wristwatch from the old Mac days. 🕛🕑🕒🕓🕕🕖🕘🕚 perhaps that will save resources.
It’s a web app and you just showed we can do it in text with Unicode and a modern browser. This bug is a level of self-inflicted, shouldn’t-be-in-the-realm-of-possible problem I struggle to comprehend. It’s the software version of not even wrong.
/ - \ | / - \ I
That’s… an expensive loading spinner.
All apps developed by AI use useless, annoying, battery draining animations. That’s why you have to close them once you’re done if you want any battery life at all. The Suno app will chew through 50% of my battery in an hour.