- It's generally bundled on most distros, or available for install in most default repositories.

- tmux sessions are available over ssh, so if I can continue where I left off over ssh (this is probably my main use case).

- I can full screen my terminal instead of having multiple terminals, and split in tmux. I usually split vim buffers, but then keep a terminal split beside it or in another tmux window.

- It's keyboard-driven, and universal across different window managers. Even if I switch from MacOS to Windows or to an X11 distro, tmux will still have the same keybinds using the same configuration language. I can also use vim keys to navigate the scrollback history.

- Its config language is simple enough for the modifications I personally need. I haven't felt that I need to learn the syntax beyond the basics.

- Knowing tmux is also a helpful skill for managing servers, which I do from time to time (my raspberry pi is still running a tmux session from when I last rebooted it).

* Spend some time learning keybindings and commands. Just an hour or two should be enough.

* Learn about the top plugins and install them. There's a plugin that saves and restores your session, I forget the name, but it's great

* If you use vim, set up both vim and tmux with the right plugins so that the same keybindings navigate across both vim and tmux splits seemlessly.

without tmux/screen though, it's much harder, even less reliable, to work over ssh, so it becomes natural need for such sort of tools.

Say I use screen and later tmux since I believe ~ 2010 but not using "advanced" features like "panes" and screen splitting every month, most of the time for me it's just switching between windows in session and different sessions (not that often) and that's all.

As a helper, for some projects, I do use predefined layouts (say first 4 windows opens with inventory dir, other 2 with root folder of ansible repo) so on, but need this also not very often, like when laptop reboots (which is every ~ 3 week on Win11 nowdays)