Hacker News Reader

Because if your network drops the connections, you can resume with tmux or screen, but not with vanilla ssh.

This is solved with mosh: https://mosh.mit.edu

Uses UDP/protobuffs so network connection can be lost/changed/etc.

And since almost nobody uses mosh (and let's not talk about security implications of its implementation), problem is not really solved at all.

You know, from a practical point of view.

Not sure if you're aware but iterm2 (v3) has tmux support so you can have the benefits of both.

Why would you prefer multiple ssh sessions over a single ssh session and tmux with iTerm2, which will let you keep the tabs (and when you make a new tab, automatically make it a remote connection).

Look at 'tmux -CC', it's really great.

I use a jump-server, so I can ssh in, and connect to an existing tmux session. If I handled my terminals locally, I wouldn't be able to do that.