Terminal emulators benchmarking suite (2018)
github.com
github.com
Performance tests somehow involve both Java and Python. I don't think that is how you do it. :-)
I mean, it's very often that one wants to copy part of the output of the previous command, and it sucks to have to reach for the mouse when the part is right there! just 1 or 2 lines above the text cursor. keyboard-select allows me to grab it in around 5 quick keypresses. It's also been tremendously useful to quickly determine if the big output of the previous command contains some piece of text without having to re-run it with grep repeatedly while adjusting the search.
That extension definitely has its warts like what happens when you go to the top of the buffer and select everything to the bottom (gVG). It causes the last screenful of text remain in a highlighted state as if it was originally like that. The ability to work on urxvt extensions is actually making me consider taking up perl.
But there's something about using the default system tools that keeps me attached to Terminal.app.
The big thing that keeps Terminal in my dock is iTerm's sometimes flaky Unicode support. In Terminal it always works. In iTerm, it's about 80/20.
I still use iTerm when I'm doing something requiring a bunch of panes. But if I'm doing something Unicode-heavy, it's Terminal.
I did find ~ on a home dir that took 1.5 seconds to do find ~ >dev/null
I ended up running on a version of mrxvt using bitmapped fonts which took 8 seconds. Scalable fonts took 35 seconds.
A VTE based terminal emulator took 394 seconds to display the same output.
In the previous tests I read, mlterm dominated in latency. Here, the tests do not give numbers
So I recommend to just ignore this entirely and evaluate which terminal emulator you want to use solely by actually using them.