4 ms·
@hutrdvnj I'm sorry, what ?! I use SSH a lot every single day. Not once have I thought "sheesh, this is slow". Before SSH became the default, I spent even m
by traceroute66 6y ago
@hutrdvnj
I'm sorry, what ?!
I use SSH a lot every single day. Not once have I thought "sheesh, this is slow".
Before SSH became the default, I spent even more of my life on Telnet. Same again, never had a problem.
I also sometimes do console connections to switches and routers.
The only lagging I've ever seen in a terminal window is when I've been on the end of a poor internet connection !
And yes I've done it on 4k displays and multiple monitors and multiple terminals.
I've never observed any flicker either (and yes I use non-standard "modern" fonts).
I've never had problems with Microsoft Word or Notepad either !
I'm sorry but I fail to see why a terminal emulator needs the same power as Photoshop or your favourite game.
Frankly I would put a GPU-accelerated terminal emulator in the category of "product solving a problem that doesn't need to be solved".
- hutrdvnj 6y agoI'm very sensitive to terminal latency and I find terminals like gnome terminal and the like are simply too slow for me. I use xterm on daily basis because it provides the best latency. https://lwn.net/Articles/751763/ https://lwn.net/Articles/751763/ I know it's not an issue for many and they tell you "excuses me, what?", but I can tell you, it's a thing.
- dmos62 6y agoIs there a specific scenario where you notice latency?
- hutrdvnj 6y agoYes, always. I can immediately notice the difference when I type on lets a gnome terminal vs. xterm. But it's not only related to terminals. I have the same issue with editors. For example, the Atom editor is unbearable slow, VSCode is slow, Vim with a few plugins (incl. syntax highlighting and the like) is okayish and plain vi is fast. At least that's how I experience it. I decided to go with vim + plugins, because it provides the best tradeoff in terms of features and latency.