Anyway that being said I have some collegues that are not bothered by lagging mouse cursors and other janky stuff so I can somewhat understand that this might not matter to some people.
edit: I just tried out st again on my gnu/linux machine and it seems to be fine with respect to input latency so I guess its not all too bad of a terminal emulator. Maybe it only sucks on macOS.
Luu also had this to say about the experimental setup for st:
> st on macOS was running as an X client under XQuartz. To see if XQuartz is inherently slow, I tried runes, another "native" Linux terminal that uses XQuartz; runes had much better tail latency than st and iterm2.
Maybe it matters, maybe it does not. But I feel like picking your terminal comes down to a lot more than a single metric and input latency experiment.
There's another set of latency measurements here: https://tomscii.sig7.se/2021/01/Typing-latency-of-Zutty In those, st is roughly similar in performance to urvxt and Alacritty.
I guess accurately measuring latency is hard.
The only thing I'm aware of that doesn't work is kittens inside tmux.
> [PARSE ERROR] The application is trying to use xterm's modifyOtherKeys. This is superseded by the kitty keyboard protocol: https://sw.kovidgoyal.net/kitty/keyboard-protocol/ the application should be updated to use that