The real advantage of Kitty over iTerm2 is that it's cross platform (Windows too), so your config files and workflow are consistent across different machines. Also, I'm starting to actually prefer using config files instead of GUI.
I think the confusion is due to the putty fork that's also called kitty.
wezterm is actually cross-platform and has great support for wsl2 as well. It also comes with a mux component which moves the mux stuff to your local machine and eliminating a lot of issues with running tmux/screen.
I looked into alacritty and kitty as well. Aside from being the best terminal for my needs, wezterm's developer is also pretty friendly and open to issues/PRs and is very responsive. I like the tool and the project so much that I help out with little things like packaging whenever I can.
Thanks for this reminder, I had peeked at wezterm a month or so ago and it sounded slick, but I was pretty happy with my iTerm+tmux setup. Just got a chance to play with wezterm a bit, and I think it's going to be my new term, because:
- The ssh mux seems to work at least as well as mosh+tmux.
- It has decent keyboard Copy/QuickSelect/Search (I liked tmuxes, but didn't get that at my native terminal).
- Runs on MacOS and Linux, my work and home environments.
Yes wez's mux is pretty nice. It will probably get better too. I think it has some mosh-like functionality too. I like that my terminal behaves the same locally and running as muxed domain on a remote server. One less set of shortcuts to remember. If it's not clean I mean for operations like copy/paste yes, but also starting a new tab (which will open a tab in that domain), splitting the current view etc.
Wezterm (kitty too) is really a great piece of software, I use terminals 12 hours a day, but I did not spent a lot of time configure them, but this article is inspirational.
PS: kitty developer is the same developer of calibre, another beautiful software.