I can see how that would be a great solution on Windows, since there's no decent built-in TTY (prior to recent builds of Windows 10). It's advertised as an "ssh client" which is great there.
But I don't know why anyone would choose to use that on a Mac. The UI requires initiating connections to remote systems (or "localhost") through the GUI -- which feels really backward when you can just open a new window/tab on any other terminal app (for local tty sessions) or run ssh from the command line (for remote sessions).
I wasn't even thinking about local term vs. remote until you mentioned it, but you're right.
I guess it's because I don't use a Mac very often and when I do I don't usually have a reason to use the local terminal. I find that's true on Windows as well, I don't often need to use the command line.
OTOH, I'm SSHed into remote Linux servers 40+ hours a week.
But I don't know why anyone would choose to use that on a Mac. The UI requires initiating connections to remote systems (or "localhost") through the GUI -- which feels really backward when you can just open a new window/tab on any other terminal app (for local tty sessions) or run ssh from the command line (for remote sessions).