Your other criticism I agree with.
That's not my problem. My problem is that they never stop animating. For me and many other people, when something is moving in our visual field, it is very, very difficult to read the text next to it.
Full disclosure: I'm autistic. I was wondering whether I should mention that. All the issues that I mentioned exclude me from using this resource. So maybe we could call these accessibility issues instead of usability issues. When I disclose that I'm autistic, it tends to evoke two types of responses:
1) Oh, sorry, we'll make it accessible. But they do it out of shame, which I don't like. I'd rather it's out of empathy.
2) You're too small of a segment to care about.
But I'm beginning to think that the only difference between usability and accessibility is the size of the population that's being excluded by the design. I chose to keep my autisticness separate to see how people responded when I presented this as a usability issue instead of an accessibility issue.
I'm only asking that designers have empathy for all possible users of their media. That's all. That's what good design is supposed to do.
I feel you. I can't have autocomplete on when I'm coding, partly because having video game stuff happening in my field of view while I'm trying to focus throws me off. I'd rather just remember the name.
Then it would still loop for you, but not negatively impact people who are using reduced motion settings in their browser/OS.
