4 ms·
> Let’s be honest, none of us are sitting around waiting for our complex IDEs to render characters on the screen. No one really cares if it’s 1ms or 30ms or eve
by formerly_proven 6y ago
> Let’s be honest, none of us are sitting around waiting for our complex IDEs to render characters on the screen. No one really cares if it’s 1ms or 30ms or even 200ms.
I actually do, because I'd like for IntelliSense and clones to save me some typing, but often that doesn't quite work out, because they're too slow (inconsistently slow, too). I'd also like it if my IDE or Word editor could highlight errors in realtime, but in reality it's more like a couple seconds delayed, so I have to navigate a significant distance back to correct them, instead of being able to fix it almost on the spot.
- PragmaticPulp 6y agoThat’s a different topic, thought. The OP posted about typing latency, not the latency of additional complex features. It’s not exactly fair to claim that software is “slower” than old software when the software you’re comparing to doesn’t have those features at all.
- justin66 6y agoUI latency is UI latency, and the problem in both cases is due to what markstos mentioned in his initial comment: the increasing internal complexity of the software stack used to develop the software. It's not like modern hardware isn't fast enough to do literally everything that needs to be done locally with minimal UI latency.
- 6510 6y agoI'm guessing 1000x