There's a pretty large contingent of developers that follow the likes of Casey Muratori and Jonathan Blow who view such dropped frames and input latency spikes

There's a pretty large contingent of developers that follow the likes of Casey Muratori and Jonathan Blow who view such dropped frames and input latency spikes as a canary for "this software is written wastefully and without competence". It's not a terrible take to be honest: on a modern machine why on earth would a _text editor_ be unable to process frames upwards of 144 Hz? It implies a technology stack built on an unknowable jungle of wasteful dependencies. In other words, I don't think it's per se about a couple of dropped frames here and there, it's about a plumage display to other engineers with the same values.