News for hackers. Stuff that matters.
Re:Measuring keyboard-to-photon latency with a light sensor by chmln on Sunday May 31, 2020 @12:38PM (#23370671)
Sadly, alacritty feels like such a waste of effort. The input lag is pretty bad, and text processing performance is a non-issue with most terminals. I've used xterm for years and never felt it was too slow at that.

Latency makes much more difference in how fast a terminal feels. This is where kitty does a fantastic job, even letting me trade some CPU cycles for really low latency with its options. I can strongly recommend it to anyone who values low latency.

Re:Measuring keyboard-to-photon latency with a light sensor by riquito on Sunday May 31, 2020 @05:53PM (#23373116)
I love it, I use it daily on Fedora and MacOS and is the easiest to configure and fastest terminal I've used so far (previously my main terminal was urxvt in daemon mode, a feature I still hope to see in Alacritty).

Christian Duerr and friends are doing a great job, please continue to work on it.

Re:Measuring keyboard-to-photon latency with a light sensor by ubercow13 on Sunday May 31, 2020 @02:39PM (#23371567)
alacritty still has the best font handling/rendering from my comparisons, though kitty's latency is very noticeably better
Re:Measuring keyboard-to-photon latency with a light sensor by aslpavel on Sunday May 31, 2020 @03:52PM (#23372157)
alacritty is actually pretty bad at font rendering quality, at least on macos, it looks worst in comparison to all terminal i've tried https://github.com/alacritty/alacritty/issues/486
Re:Measuring keyboard-to-photon latency with a light sensor by ubercow13 on Sunday May 31, 2020 @04:22PM (#23372379)
Oh interesting. On Linux it's clearly better than kitty: https://i.imgur.com/fzAPhlN.png

Last time I checked it also had the best unicode handling too, in terms of reliably falling back to some other font for missing codepoints and getting the display of oversized characters right.

Re:Measuring keyboard-to-photon latency with a light sensor by chaorace on Monday June 01, 2020 @10:43AM (#23378973)
It's not immediately obvious which terminal is which. I feel like the text is sharper and, as a result, more readable in the right window, not sure if that agrees or disagrees with your thoughts
Re:Measuring keyboard-to-photon latency with a light sensor by ubercow13 on Monday June 01, 2020 @12:56PM (#23380671)
The right one is kitty. Look how the italic characters have uneven spacing, eg. the 'l' in 'bold', and some of them are chopped off, for example 'M'. Look how the percent sign on the bottom looks like it's been stretched and the circles aren't the same.

The right hand one is sharper but I have my freetype tuned to look like the left one, which looks the same as every other application on my PC. kitty is doing something completely different and incorrect.

Re:Measuring keyboard-to-photon latency with a light sensor by StavrosK on Sunday May 31, 2020 @08:02PM (#23374245)
What are the low-latency configuration options you mention?

EDIT: Actually, I use a Bluetooth keyboard, so it's probably moot.

Re:Measuring keyboard-to-photon latency with a light sensor by ubercow13 on Sunday May 31, 2020 @08:04PM (#23374250)
'repaint_delay' and 'input_delay' - there are explanations of each in the default config file