Earlier quoted context omitted.
4. If they previously had a 60Hz monitor, and upgraded to 120Hz or better. This improves both motion quality and latency. When poorly designed software makes you wait multiple frames, halving (or better) the frame time makes a noticeable difference.
I find this one hard to swallow. On 60Hz software is already the bottleneck even on high end hardware. If anything, it’ll drive a perfectionist mad because crappy software that the high end hardware allowed to operate just over that threshold (say 64Hz) would suddenly be exposed. I think jitter is more important than FPS and until software has caught up (likely never) I would rather cap the frame rate at 60 FPS and e…
A lot of software, especially websites, have annoying waits for Vsync that are not needed in them.
When you update styles that triggers a reflow or repaint, then you can introduce a wait for VSync in your website thats stalls flow until it is finished.
If you add 3 frames of delay at 60fps then it's 50ms of delay, and only 25ms at 120fps. It doesn't sound like a lot, but that 25ms can be the difference between feeling totally fluid and not, and a lot of websites are even worse than that.
Software can be IO bound, Network bound, CPU bound, memory bound.
Modern software is Vsync bound!