There are moments that tmux's persist session won't work well such as opening nested SSH sessions to another machine with nested tmux to keep the session. Also, tmux does not handle SSH sessions, so if a SSH session disconnected (e.g. WiFi signal lost, your macBook gets sleep mode), you need to manually restart the SSH session and run tmux again, whereas Blink and ET never disconnects the SSH session.
On top of that, I use both tmux and Mosh at the same time. You don't need to use tmux exclusively.
I meant, you don't need to get scared. Both ET and Mosh built on top of SSH and there never be critical errors when dealing with their shell. Though both of them requires installations on the remote but they are a single zero-config packages: just install a package (not "a bunch of") and that's it. No config needed, even no background systemd services needed.
Right, I see how it can be more convenient but I also see caveats so I’m not sure if I should bother. I’m not really a fan of installing much, either: often I don’t really want to do a whole install to get into a machine (some random AWS for instance) or I just can’t (not my machine, no admin privileges, paltry package manager, …)
> There are moments that tmux's persist session won't work well such as opening nested SSH sessions to another machine with nested tmux to keep the session.
what difficulties are you facing there? i use tmux deeply nested without problems. one trick i use is to change the tmux command key to be something different on each nesting level.
If you just want a persistent connection, you never have to press the command key or even acknowledge it exists, do you? And you didn't answer what difficulties you've personally faced.
If I just want a persistent connection, then the nested tmux that takes 2+ useless lines in the bottom already falls into the "it doesn't work well" category.
And I what I said that the problem was the moment I have to have different tmux config for every machine, just like she/he is doing.
I guess I just don't understand why you need the tmux command key at all. If you pretended it didn't exist, what feature would you be losing out on that mosh has?
And when you're setting up a server it's easy to turn off the tmux status bar.
indeed. the only thing i need to do is copy a config file to set up the command key. the main use of the command key is to switch terminals and to access scrollback. beyond that, the key is rarely needed. working in any terminal is the same no matter how deep the nesting. i don't notice it.
the multiple toolbars don't bother me either. they can serve as a visual aid to recognize where i am. each terminal looks different. but in reality i don't pay much attention to them.
On top of that, I use both tmux and Mosh at the same time. You don't need to use tmux exclusively.
I meant, you don't need to get scared. Both ET and Mosh built on top of SSH and there never be critical errors when dealing with their shell. Though both of them requires installations on the remote but they are a single zero-config packages: just install a package (not "a bunch of") and that's it. No config needed, even no background systemd services needed.