Last I personally used Alacritty was 3-4 years back on Linux w/ wayland got some weird rendering bugs, switched to st (https://st.suckless.org/) for a good while.

When I got a Macbook last year, I did a "best terminal macos" search and evaluated multiple terminals; kitty, ghostty, iterm2 and wezterm.

settled on ghostty because it just felt faster for terminal refreshes when I use vite, had tabs, could easily theme it to use ayu-dark. Nothing too extreme, just personal reasons

iterm2 was fine as well, nothing special; wezterm and kitty just felt like linux apps that were on macos as well. YMMV.

I use alacritty. I tried ghostty but not supported on my old home mac, felt slower, and some of the config was not robust. Same with Wezterm, felt slow. Alacritty has worked with no problem everywhere I installed it. Only annoyance was once when the config changed from yaml to toml. Other than that, happy user of alacritty.

I still do. It's faster than Kitty and Ghostty, and I don't make use of the extra features those provide. I don't use glyphs nor rendered images, and I use a tiling WM so tabs aren't that important to me. Alacritty does what I need it to, and does it well.

Been driving my use for the last year or so, perfect as a thin wrapper around tmux (which is the same on macOS and Linux).

I'll give iTerm2 another try, has many shiny features like touchID-sudo and such, otherwise don't understand what could possibly be better in ghostty/kitty

I've been using alacritty for ... I don't know, but many years, and haven't once been tempted to switch away.

chiming in as another alacritty (linux) user. kitty never seemed to be much of an improvement for my own workflows, and on my mac, ironically enough, ghostty was having issues with escape sequences when using the terraform CLI, so i stopped using it there.

Definitely, been using it for years and it's one of the upgrades that has genuinely made every day noticeably better

I did for several years but moved on to foot due to minor Wayland quirks I don't even remember.

Happy alacritty user here (Wayland + sway)!

Can't comment for others but for me I find zoc or in that regard, a SSH client useful for the following

1. Remembering multiple hostnames and keys in a centralized location

I manage a fleet of VPSs, whose hostnames, credentials I don't always remember off the top of my head. Writing ssh -i <identity> <hostname> gets tedious when I'm wrangling multiple of them over a single session

2. Faithful terminal emulation

Zoc does a great job at emulating a plethora of terminals; it's not a do or die feature, but nice to have.

3. Separation of concerns

This is a personal reason, but I like having two different applications while I am doing something that needs me to SSH to multiple VPSs, my main terminal will have local commands, local file editing, etc while my SSH client will only be used for remote connections and management. Just helps me keep things tidy for myself.

Also as I mentioned in the parent I primarily use my main terminal to SSH; but for the cases mentioned it's nice to use a separate client.

To see a clear and categorized list of saved sessions, for example I have 300 different saved sessions and that's not even a tenth of the hardware we have. They are categorized, so I can quickily find a specific one I need and connect to it in one click. This also mean that I can see what sessions I do not have saves and immediately go to a page with all information. Telnet sessions also live there, seamlessly. And finally I can have saved arbitrary commands, different per each session for the quick use. Especially useful with inane kilometer long k8s commands.

Just use picocom in any terminal you like: https://github.com/npat-efault/picocom (unmaintained, but works fine and there is a ng fork: https://picocom-ng.oddbit.com/). Or minicom or screen, but those are more bloated.

There is little reason for SSH client to be integrated into a terminal emulator. Admittedly, my favorite kitty has a wrapper around OpenSSH, to fix terminfo and stuff, but it doesn't tries to re-implement the protocol. There is even less reason for serial port terminal to be a part of a terminal emulator - serial port terminal simply sets baudrate, remaps some control characters and gives you an escape key, it is not connected to rendering in any way.