Afaik the director has been a dbag with his projects re contributors. Calibre and kitty.<p>It is his project and he doesnt owe any one anything, bit i would take my Limited OSS Aattention elsewhere.
It's a very fast terminal but has some graphical artifacts in vim for me with integrated terminal.<p>I use alacritty now. I also used wezterm for a while, it's really good but feels slower.<p>Overall we are spoiled with choice. :)
My favourite part of kitty is the "grabbers", like "ctrl+shift+p f" pops up vim-sneak like tags on all the file paths visible in the terminal. Swap f for h and it will let you select a hash. I would love it if that became a standard across terminals
<a href="https://github.com/wez/wezterm" rel="nofollow">https://github.com/wez/wezterm</a> is another great option. I find it's configuration is a lot simpler (and it's in lua) and it's also very fast.
I made the switch from iTerm2 last week and loving how blazing fast kitty is. I also found some kitty.conf files written for iTerm users so I felt right at home pretty quickly.<p>The only feature I miss from iTerm2 is the ability to maximize a pane (on iTerm the default keybinding is cmd+enter) but I've read the stack layout mode can emulate that on kitty (still need to try it out and get a sense of UX) but it's not a deal-breaker for me.
What is the virtue of a GPU-based terminal vs. non-GPU-based terminal? I'm not grasping what "GPU-based" means here. The software must still load from storage or net to an OS layer, which still runs on a CPU.
Zutty is also cool: <a href="https://tomscii.sig7.se/zutty/" rel="nofollow">https://tomscii.sig7.se/zutty/</a><p>It's correct (like XTerm) while still being very fast.