[hyperman1]

I started to use tmux on remote machines to stop them disconnecting me when the network changes or the laptop sleeps. (Damn you systemd for breaking that, too)

Then I started multiple tmux panes remotely because it was great for dumping the long process monitoring next to the long process

Then I started using tmux panes remotely for task switching.

Then I started using tmux locally because I already knew all the keybindings and tricks.

And there are still multiple browsers, IDEs and whatnots in other windows.

At no point, the points the article touches had any relevancy. It just grew on me. So you all do whatever floats your boat, and I'll continue doung mine.

[tetha]

Yeah, I've also achieved a degree of Zen about things like these.

Like, I'm current on-boarding some guys onto linux workstations and linux administration, and honestly, there are many ways of holding the duck and in a lot of situations, most ways of holding the duck work equally well. I can show you two or three ways I found to work well to hold the duck, but it's still up to you to find your perfect duck rotation.

Like, I use i3 as a tiling window manager. But if I'm honest, I don't really use the tiling that much. The most tiling I tend to use is having 2-3 shells eithes stacked as dishes or one tall and a stack of dishes next to each other. Otherwise it's usually a 50/50 split of screenspace of just a full screen window. I just can't focus on more at the same time anyway. The latter use case can be had by using gnome or KDE with about the same amount of key strokes. Tmux offers it equally well, as Kitty windows do.

Personally I enjoy i3 on my workstation because a few key bindings and workflows have found their way into my lizard brain, but the newer guys relying on other window managers aren't much slower for most use cases tbh.

Similar, I've used multiplexers, terminals with such features. Currently I'm experimenting with rofi and single-purpose named kitty-terminals to easily find or launch shell environments I need. But honestly, everything works with little difference in efficiency imo.

It's more about finding something that clicks for you than doing the dogmatically correct thing. That's the wonderful thing about a linux desktop, and also it's biggest curse.

[freedomben]

Just a side note, I think mosh is a much better tool for stopping the disconnections from network changes or laptop sleeps. It uses UDP under the hood instead of TCP so it seamlessly supports roaming (changing of IP addresses). Also brings some great performance improvements as well, especially when the remote process is dumping lots of text to standard out

[dingaling]

After a while though, particularly on flakey connections, I end up with dozens of stale mosh sessions on each server, all listening for inbound connections that will never come.

The quickest way to clear them seems to be pkill mosh and then reconnect. It's a known bug with no anticipated fix.

[mmh0000]

Yes, mosh is great.

Except, neither RHEL nor SLES include it in the base repo. This means getting it approved and installed on servers in most enterprises is never ever going to happen.

Thus, mosh is dead to me (a poor sysadmin who lives under constant fear of The Security Team).

[freedomben]

Good point. It also requires opening some UDP ports, which many security teams balk at. Real shame though because it makes life a lot better.