The argument here seems to be: “the features you like about terminal multiplexers should be built into your terminal emulator, or your window manager, or I don’t see why they are really necessary.” Plus some complaints about influencers.<p>Sure, I’ll just replace my perfectly functional window manager so I can avoid using a terminal multiplexer.<p>Except I’ll still want a terminal multiplexer on servers, so I still need to be familiar with the way the tool works and I’ll still be happier if I have a nice config (sidenote: the article complains about needing very complicated configurations, but tmux is fine with like… 10 lines of configuration? You can solve the problem of over complicated configs by just not doing them).<p>Overall it kind of feels like hipsterism or engagement bait. Complaining about “content creators” is a very popular way to show off your bona fides nowadays. I guess this is just going back and forth on “no, you are the influencer/engagement fisher” but I think tons of people have been using terminal multiplexers for decades because they are boring and practical. If someone made a YouTube or a TikTok about them, I guess… I dunno, let the kids have nice things too, <shrug>.
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)<p>Then I started multiple tmux panes remotely because it was great for dumping the long process monitoring next to the long process<p>Then I started using tmux panes remotely for task switching.<p>Then I started using tmux locally because I already knew all the keybindings and tricks.<p>And there are still multiple browsers, IDEs and whatnots in other windows.<p>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.
I do, because I'm a professional who needs to get work done, instead of dicking around in React all day and writing edgelord blog posts about 40-year-old tools.
This is a great example of engaging writing that fails to convey an appreciable message and even though I use tmux locally and I had a thought the other day that I should stop, I hope that the author can channel their energy toward a better formula for thoughts.
I tend to agree with this guy. I like using multiple windows or tabs in konsole and dont use tmux etc. If you're spending time sshing into remote machines tmux etc is the way to go. Although when I remote in I still don't use tmux or screen in general. I prefer using nohup for long running processes or even just keep the laptop from sleeping by plugging it in.
Arrogant and pointless? You want to use a GUI, go for it.<p>To me, just because most of my workflow doesn't need to change irrespective if I'm working locally or via ssh, is already making terminal multiplexer a win.<p>Also, there's something to be said about terminal just being a more productive way to work with computers. The constrains that a terminal puts on software used in it, make the individual pieces compose with each other way better, precisely because text composes better than graphic interfaces. (That's why "visual programming" will always suck.)<p>My workflow for decades now is entirely terminal with terminal multiplexer and a browser window. The graphical interface works better for exploratory work when I'm mostly navigating and consuming information, like clicking around the web, the textual interface works better for actual precise control and interaction with software. The "GUI" for me is just for changing if my browser/terminal are displayed side by side or maximized and switching between them.
From TFA: My impression is that the sole purpose of the terminal multiplexer hype train stems from a perceived sense of pseudo-elitism…<p>—-<p>Whoa there buddy.
It’s fine to say: “I tried a thing, and it just wasn’t for me”.<p>But to proceed from that point and onto: “so rather just letting things be, or making a good-faith effort to understand those with differing opinions, I’m going to project and harshly judge them” is such a downer.<p>I guess what I’m trying to say is, I tried reading this blog and it just wasn’t for me.
I mean, if I'm having fun and I'm productive, why do I have to justify my setup? But if I would, I'd say that VSCode didn't support all of the Vim functionality, so I started using NeoVim and to avoid managing multiple terminal windows I use tmux.
Feels like it's totally missing the point of why tmux is used on desktop and in a very arrogant tone.<p>Windows manager saves layouts. I want to save both layout and states. I want to be able to quickly switch from one project workspace to another, without having to use ctrl+z and fg or creating term windows everytime.<p>Also, a lot of people use one workspace for one app on their WM (1 for terminal, 1 for browser, etc...)
I like that my terminal has its own workspace, so I don't have to pollute the workspaces of my WM with tons of different terminal windows.<p>Maybe spend more time understanding the problem that is trying to be solved before writing a long ass arrogant article?
I use screen all the time in an SSH session. Locally, not so much.<p>Although if I'm running something that I know will take hours, I tend to run that in Screen because I'm likely to nuke the terminal by accident.