But if I hibernate my computer twice a day, once to take it to work and once to bring it home, then twice a day my SSH connection will be killed due to hibernation (or even if I didn't hibernate it, it would be killed during network disconnection), meaning this setup is only good if everything I do fits into a single eight-hour workday, or if I work exclusively over a cellular connection with transparent network migration and never put my computer to sleep. Simpler to just have a program running on the server that I can attach to.

I know what you mean, but again, I never need that and the investment in tmux is to high for edge cases. Btw: Long running jobs are easy with a cron job:

echo "/path/to/long_process.sh" | at now + 1 minute

You never let your PC sleep when you're having lunch or something?

I do. No Problem closing the lid on my MacBook M1. I can open the lid and keep on working where I left.

I use kitty and the kitten ssh [1] to login easily to remote hosts, and automatically setup the environment.

I can use a simple bash like

  #!/bin/bash
  kitty @ launch --type=tab --title='Server 1' bash -c "command1; exec bash"
  kitty @ launch --type=tab --title='Server 2' bash -c "command2; exec bash"
  kitty @ launch --type=tab --title='Server 3' bash -c "command3; exec bash"

If I need several servers at once. Could be done with other shells too.

I can run loooong processes on the host with a simple bash script and the marvelous `àt` [2] command that nobody seems to know any more like:

  echo "/path/to/long_process.sh" | at now + 1 minute

And the team can reuse those simple bash scripts!

If `at` is not installed, and you need to run multiple looong tasks, try `nohup` [3]. Another lost command full of great functions like:

  nohup command1 &
  nohup command2 &
  nohup command3 &

If you and your team is happy with tmux, that's fine! But doing more or less the same things with easy linux commands is – in my opinion – the better way.

[1]: https://sw.kovidgoyal.net/kitty/kittens/ssh/

[2]: https://linuxhandbook.com/at-command/

[3]: https://www.howtogeek.com/804823/nohup-command-linux/ and https://stackoverflow.com/questions/5164985/how-can-i-use-no...

Edit: Formatting

OP here, today I learned about the `at` command. Thanks!

Knowing tmux means you can have persistent sessions between the console and the window manager, and means you can use your workflow on other people’s machines, on machines without a stable connection, and on machines without Kitty or a GPU installed. I don’t know about Kitty, and there doesn’t seem to be universal love for it or it’s author, but I can mention that tmux is scriptable which makes certain multi-shell workflows amazingly fast and useful. One web company I worked for built the dev environment around launching tmux and starting different servers in each tab automatically. This is really useful and elegant for debugging without having to sift through the combined output of these servers, made it easy to stop and restart individual servers, avoided the need to juggle files, etc. etc.. Hard to see these advantages if you haven’t experienced it, but this setup is something I’ve adopted and carried forward to other companies because it’s so nice.

What if you are running a long running and important process and your personal internet connection drops, killing your process? That's why I am fond of screen and tmux

That’s valid, but how often does it happen? It never happened to me. Long running jobs are easy with a cron job:

echo "/path/to/long_process.sh" | at now + 1 minute

And it adds the benefit to simply call that script again, if you need the same long process again.