For all the people who are doubting that applications are slow and that it must just be me - here [0] is a debugger that someone has built from the ground up that compiles, launches, attaches a debugger and hits a breakpoint in the same length of time that visual studio displays the splash screen for. [0] x.com/ryanjfleury/status/17477562194047…

Reminded me of this interesting thought experiment x.com/lauriewired/status/19220159991186…

CPU speed is not memory bandwidth. Latency and contention always exist. Long lived processes are not always the norm. In another era we would have just called this optimal. x.com/ID_AA_Carmack/status/192210077139…

There's a problem when people who aren't very sensitive to latency and try and track it, and that is that their perception of what "instant" actually means is wrong. For them, instant is like, one second. For someone who cares about latency, instant is less than 10 milliseconds, or whatever threshold makes the difference between input and result imperceptible. People have the same problem judging video game framerates because they don't compare them back to back very often (there are perceptual differences between framerates of 30, 60, 120, 300, and 500, at the minimum, even on displays incapable of refreshing at these higher speeds), but you'll often hear people say that 60 fps is "silky smooth," which is not true whatsoever lol. If you haven't compared high and low latency directly next to each other then there are good odds that you don't know what it looks like. There was a twitter video from awhile ago that did a good job showing it off that's one of the replies to the OP. It's here: x.com/jmmv/status/1671670996921896960 Sorry if I'm too presumptuous, however; you might be completely correct and instant is instant in your case.