Alacritty gets scrollback, publishes benchmarks

These benchmarks miss the point in my opinion. When I&#x27;m choosing a terminal emulator, beyond features, the one &quot;performance&quot; metric that I&#x27;m interested in is latency; nothing else really affects my workflow (positively or negatively). In the benchmarks I&#x27;ve seen of alacritty wrt latency[1][2], it doesn&#x27;t come out so well.<p>[1]: <a href="https:&#x2F;&#x2F;danluu.com&#x2F;term-latency&#x2F;" rel="nofollow">https:&#x2F;&#x2F;danluu.com&#x2F;term-latency&#x2F;</a><p>[2]: <a href="https:&#x2F;&#x2F;lwn.net&#x2F;Articles&#x2F;751763&#x2F;" rel="nofollow">https:&#x2F;&#x2F;lwn.net&#x2F;Articles&#x2F;751763&#x2F;</a>

Regarding tabs, macOS has native tab support more or less built-in to the windowing system—you can see this in action if you create a document-based app in Xcode—but your app has to be structured in such as a way as to opt into it. Have you considered opting into this or would you consider it contrary to the project goals?

Has the input latency improved any? I liked alacritty, but I switched to mlterm after a while because the input latency was really bugging me.

I&#x27;m really happy to see all the hard work come together on this. I think the project has a great new feature.

Author here; I&#x27;m happy to answer any questions!

This sounds great, especially the fact that v0.2 has much improved throughput over v0.1 in most cases. I must however echo some other posters&#x27; sentiments: latency is even more important than throughput, and alacritty&#x27;s input latency wasn&#x27;t great last time I tested it (quite a while ago). Maybe it&#x27;s been improved too, though no mention of it in the post.

What possible use cases where such high scrollback speeds could be useful?