2 ms·

Same here. And yet, nobody I've worked with over the past 2 years feels Electron based editors are slow or unresponsive. I'm not just talking about kids who hav

Same here. And yet, nobody I've worked with over the past 2 years feels Electron based editors are slow or unresponsive. I'm not just talking about kids who have never used anything else, either. Some of these people have been programming since the 80s. It's like some people are sensitive to latency and some aren't. I've also been told it's impossible to tell the difference between 60hz and 144hz. I can tell. I know this for a fact because my hackintosh will occasionally "forget" and switch my monitor back to 60hz when I wake it up from sleep. I notice immediately.

morganvachon 8y ago
I'll admit I feel the difference more on my work machine (i5-2400, Windows 7) than my home workstations (i5-6500, Antergos Linux and Slackware Linux). It's definitely there though. Slack is another offender; we use it at work and our few remaining Core 2 machines and AMD A10 machines are brought to their knees with the Slack Electron app. Those users tend to launch it in a Chrome or Firefox window and leave that running. I can also pick up on different refresh rates, and I was extremely sensitive to it on CRTs back in the 90s and early 2000s. I had to run at least 75Hz on a CRT or I'd have too much "shimmy" in the image and would get a headache in a few minutes of work. 60Hz on an LCD doesn't typically bother me unless its grey-to-grey response time is poor, and produces ghosting. Even with that I don't seem to get headaches from LCDs.
taneq 8y ago
I felt like this about microstuttering 10 years ago. My computer was running at 100fps and yet it looked jerky and nobody else seemed to notice, and it was driving me mad. Thank goodness VR came along with its extreme latency-sensitivity and suddenly everyone else cared about maximum frame time too.