I use terminology today, which is also "fast." The major issue I run into with ghostty vs terminology is that ssh in ghostty is broken due to the terminfo thing. I don't fully understand why ghostty can't pretend to be a different terminal that remotes know about (for now), but I assume there's some reason.

Have you tried the suggestions in https://ghostty.org/docs/help/terminfo#ssh? I don't know what issue you may be experiencing but this solved my issue with using htop in an ssh session.

For another approach, personally I found just doing `TERM=xterm-256color ssh <server>` more practical than the solutions at https://ghostty.org/docs/help/terminfo#ssh

That is essentially the 2nd solution recommended. I think ghostty could do this itself as a hack. If the target binary is ssh (heuristic, but, ok), inject TERM=xterm-256color into env of the child process at launch.

I guess it isn't a huge deal to have every user to modify their ssh_config instead, but it's an ergonomic pain point for many new users.

Copying terminfo around is more inconvenient than I want to put up with for now. Overriding TERM is fine, I guess.

Mostly terminology is just a fairly good terminal, so I have little incentive to switch. :)