3 ms·

There’s also the latency issue: https://danluu.com/input-lag/ https://danluu.com/input-lag/ My normal desktop has a 240hz monitor and going between that and 60

There’s also the latency issue: https://danluu.com/input-lag/ https://danluu.com/input-lag/ My normal desktop has a 240hz monitor and going between that and 60hz is an immediately noticeable downgrade in performance. Why did we accept 60hz as good enough for so long? Even CRTs commonly ran at faster refresh rates. IIRC 1600x1200@90 was what I ran back in the Pentium 3 days on a 21” Sony CRT. We still don’t have useable 4:4:4 4k@120hz on something like a 32-42” screen available. Anyway, I agree that web tech is easy to develop (not that I thought Visual Basic was terribly difficult comparatively) but there are too many layers of abstraction these days. Can we not make sufficiently advanced compilers to make these really efficient? If not, do we need to go back to tinge drawing board with libuv and event loops? Maybe interrupts and manual memory management really were better. Java for GUI apps certainly hasn’t done much to show that it’s a better solution. It’s funny but sad how these days, apt upgrade runs so fast, and compiling kernel modules happens extremely quickly, but it takes 10x as long as it did 20 years ago to schedule a calendar appointment with someone because GCal in a browser is so slow. Slack compared to curses-based IRC clients…woof.

vladvasiliu 5y ago
Well, yes, there's the display latency issue, but I think that given the state of some programs, the display lag is really way, way down the list of problems. I have a 60 Hz display, and an IPS one at that, which doesn't even try to pretend it's fast. Still, my terminal window doesn't lag behind when I type. Teams does, every time. > Java for GUI apps certainly hasn’t done much to show that it’s a better solution. Meh, I use a Jetbrains IDE almost everyday, sometimes even with Rust and pretty much everything turned on. Even on my almost eight-year-old MBP input never, ever lags like Teams does on a 6 core i7 with a "gaming" GPU. It's not as smooth as a Linux terminal, but it's never irritating. > It’s funny but sad how these days, apt upgrade runs so fast, and compiling kernel modules happens extremely quickly, but it takes 10x as long as it did 20 years ago to schedule a calendar appointment with someone because GCal in a browser is so slow. Slack compared to curses-based IRC clients…woof. Exactly. And what drives me up a wall is seeing people being resigned. Some act like they don't even notice this. I guess we may moan until we're blue in the face on HN &c, but if "regular people" don't care, no one's going to do anything about this.
- manquer 5y ago
  IDE customers care about that latency lot more than slack/teams users do. A lot of non technically focus look at keyboard while typing, they won't even notice the lag if they are not looking at the screen. If there is enough customer demand/push latency is not that difficult to solve even on electron, browsers that they based on don't have this latency problem after all. The market economics dictate features, well built apps are not what is necessarily selling.

vladvasiliu 5y ago

Well, yes, there's the display latency issue, but I think that given the state of some programs, the display lag is really way, way down the list of problems. I have a 60 Hz display, and an IPS one at that, which doesn't even try to pretend it's fast. Still, my terminal window doesn't lag behind when I type. Teams does, every time. > Java for GUI apps certainly hasn’t done much to show that it’s a better solution. Meh, I use a Jetbrains IDE almost everyday, sometimes even with Rust and pretty much everything turned on. Even on my almost eight-year-old MBP input never, ever lags like Teams does on a 6 core i7 with a "gaming" GPU. It's not as smooth as a Linux terminal, but it's never irritating. > It’s funny but sad how these days, apt upgrade runs so fast, and compiling kernel modules happens extremely quickly, but it takes 10x as long as it did 20 years ago to schedule a calendar appointment with someone because GCal in a browser is so slow. Slack compared to curses-based IRC clients…woof. Exactly. And what drives me up a wall is seeing people being resigned. Some act like they don't even notice this. I guess we may moan until we're blue in the face on HN &c, but if "regular people" don't care, no one's going to do anything about this.

manquer 5y ago
IDE customers care about that latency lot more than slack/teams users do. A lot of non technically focus look at keyboard while typing, they won't even notice the lag if they are not looking at the screen. If there is enough customer demand/push latency is not that difficult to solve even on electron, browsers that they based on don't have this latency problem after all. The market economics dictate features, well built apps are not what is necessarily selling.