jumpiness

The jumpiness of pages switching and things changing when an AI is driving is extremely disorienting.

The downside is it has a lot of weird artifacts and jumpiness.

No matter how fast the underlying action is, the jumpiness and occasional lagginess makes it feel slow to me.

As far as the jumpiness, its the gestalt of the experience, from a ton of papercuts big and small: 1.

I would have never guessed HN-books is all client-side, but that does explain the jumpiness of the UI.

They only realized I was there when I sounded the horn and seemed really surprised, judging by their jumpiness.

I am right away distracted by a huge rectangle around cursor line, current word highlighting and general jumpiness of everything.

I've been using Bluetooth mice for a long time and have never experienced any jumpiness.

May be because of their unpredictability owing to their jumpiness?

Those clients will see a bit of jumpiness in the game state, which isn't ideal, but may be the lesser evil compared to enduring more latency.

I'm sorry, the page rendering (even on Chrome) with it's jumpiness and then the click to see another 1/6 of the article is more than I could tolerate to read the actual content.

Caffeine is a no-brainer, but l-theanine is amazing in that at a 2:1 ration of l-theanine to caffeine it removes essentially all the jumpiness of the caffeine.

So the first question is whether these "jumpiness" is an inherent, desired property of GIFs or an artifact of bad renderers.

This brings me back to this question: > So the first question is whether these "jumpiness" is an inherent, desired property of GIFs or an artifact of bad renderers.

The "jumpiness" is called rubberbanding [2].

I'd argue that GIFs that exploit this property and rely on the "jumpiness" to look good are not band-limited, require a "jumpy" renderer and will suffer from the 50Hz/60Hz problem.