You might not need tmux

Summary

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. For example, if you do not set TERM with tmux properly, your colors will render incorrectly. Without tmux everything looks good, but with it things can look washed out or just wrong. So when debugging issues related to terminal features, you need to consider both your terminal emulator and tmux. Now add another layer like ssh and you're really pulling your hair out. Another example is buffer scrollback. It's one of those things where you have to learn the tmux way of scrolling a window. You get used to it, of course, but it's just not great. And what about mouse select to copy/paste? It works most of the time, but sometimes tmux gets ignored and I'm selecting across splits which makes the thing I'm copying impossible to grab without bailing. Another issue I ran into a couple of times is the lack of experi...