A quick glance at the docs tells me this implements its own multiplexing all the way down, as opposed to integrating with tmux like iterm2 does.

The downside is that this requires installing the multiplexer on the remote machine, whereas iterm works with the much more prevalent tmux install.

Not sure what this means in terms of performance, I've never had any issues running remote tmux in alacritty or in iterm (via `tmux -CC`).

I don't have any use for running tmux locally, but I would sure love to be able to have actual windows for remote sessions (I use i3 and would prefer to manage all windows through that).