Hear me out, I can already read the descenting opinions:
But I need session persistence!
But I need split windows!
But I need to group windows per project!
But I need lots of terminals inside of a remote server!
I had the exact same response whenever someone would argue against using tmux . For context, I've been a huge fan of tmux and have been using it as a daily part of my workflow for 7+ years. Whether I'm developing on my local machine or in SSH, I was using tmux .
However, a couple of years ago I stumbled across a GitHub issue in the kitty project that has stuck in my mind like an itch that I cannot scratch.
In summary: multiplexers add unnecessary overhead, suffer from a complexity cascade, because they actually have to translate escape codes, modifying them in hackish ways to get them to work with their concepts of windows/sessions.
And then a couple of weeks ago I watched this excellent interview from linkarzu and kovid (creator of kitty). In it, they discussed tmux .
I have to say, the arguments are convincing. Over the years, I have had a handful of problems with tmux that were not necessarily deal breakers but very annoying to deal with on a regular basis.
... continue reading