These benchmarks miss the point in my opinion. When I'm choosing a terminal emulator, beyond features, the one "performance" metric that I'm interested in is latency; nothing else really affects my workflow (positively or negatively). In the benchmarks I've seen of alacritty wrt latency[1][2], it doesn't come out so well.<p>[1]: <a href="https://danluu.com/term-latency/" rel="nofollow">https://danluu.com/term-latency/</a><p>[2]: <a href="https://lwn.net/Articles/751763/" rel="nofollow">https://lwn.net/Articles/751763/</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?
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' sentiments: latency is even more important than throughput, and alacritty's input latency wasn't great last time I tested it (quite a while ago). Maybe it's been improved too, though no mention of it in the post.