Chapter 10: Conclusion - Choosing Your Champion

In which we reach the end of our journey, make peace with our choices, and realize the real terminal multiplexer was the sessions we detached along the way

The Answer You’ve Been Waiting For

After nine chapters of comparison, analysis, and occasionally petty rivalry, you deserve a definitive answer. Which terminal multiplexer should you use?

Tmux.

Unless you shouldn’t, in which case, Screen.

Unless you should use both.

Or neither, if you’re one of those people who opens 47 terminal windows and calls it “organization.”

The Real Answer

The truth is, asking “Screen or Tmux?” is like asking “Vim or Emacs?” or “Tabs or Spaces?” or “Star Wars or Star Trek?” The answer depends entirely on:

Your environment: What’s available? What’s standard?
Your workflow: Simple sessions or complex layouts?
Your team: What does everyone else use?
Your patience: For learning curves and configuration
Your philosophy: Minimalism or feature-richness?
Your beard length: (Longer beards correlate with Screen usage)

The Decision Tree

Start Here
    ↓
Is it already installed?
    ├─ Yes → Use it
    └─ No ↓
       Can you install software?
           ├─ No → Use what's there (probably Screen)
           └─ Yes ↓
              Is this a modern system (post-2010)?
                  ├─ No → Install Screen
                  └─ Yes ↓
                     Do you value features over simplicity?
                         ├─ No → Install Screen
                         └─ Yes ↓
                            Do you enjoy reading documentation?
                                ├─ No → Install Screen (and suffer)
                                └─ Yes → Install Tmux (and prosper)

What We’ve Learned

About GNU Screen

It’s older than the World Wide Web
It works everywhere, even on systems that shouldn’t exist
Its configuration looks like encrypted transmission from aliens
It refuses to die, like COBOL or fax machines
It does exactly what it promised to do in 1987, no more, no less
System administrators love it with stockholm syndrome intensity

About Tmux

It’s what Screen would be if designed this millennium
It has features you didn’t know you needed until you have them
Its documentation is actually helpful
It has a plugin ecosystem that’s surprisingly active
It makes you feel modern and sophisticated
Developers under 30 have heard of it

About Terminal Multiplexers in General

They’re essential once you start using them
They’re impossible to explain to non-technical people
They make you look like a hacker from a movie
They save your work when everything else fails
They’re the reason you have trust issues with regular terminals
They’re probably running forgotten sessions on servers worldwide

The Zen of Terminal Multiplexing

Persistence is a virtue: Your sessions outlive your connection
Screens within screens: It’s not confusing, it’s powerful
The prefix key is sacred: Choose wisely, change rarely
Configuration is personal: Your dotfiles are your identity
Detachment is healthy: Both from sessions and emotionally
Windows are cheap: Create liberally, close sparingly
Panes are powerful: But with great power comes great confusion
Copy mode is essential: The mouse is optional
The status line is your friend: Even if it looks ugly
There is no perfect setup: Only the setup that works for you

The Future of Terminal Multiplexing

What’s Coming

AI Integration: “Copilot, create a development session for React”
Cloud Native: Sessions that follow you between machines
Better Mobile Support: Because coding on phones is masochism we embrace
VR Terminals: Multiple screens in virtual space (why not?)
Quantum Multiplexing: Sessions in superposition until observed

What’s Not Changing

The prefix key debate
Configuration file complexity
The Screen vs Tmux holy war
Forgotten sessions running forever
The inability to explain them to your manager

Personal Recommendations

For the Beginner

Start with Tmux. It’s modern, well-documented, and has a gentler learning curve. You can always learn Screen later if needed.

For the System Administrator

Learn both. Screen for ancient systems, Tmux for everything else. Your ability to use both makes you invaluable.

For the Developer

Tmux, unless your team uses Screen. Features matter when you’re living in the terminal 8+ hours a day.

For the Minimalist

Screen. It does what it needs to do, nothing more. You probably compile your own kernel too.

For the Power User

Tmux with every plugin known to humanity. Your config file is longer than some programs.

For the Pragmatist

Whatever’s installed. Both tools solve the same core problem. The best multiplexer is the one you’re using.

The Cultural Impact

Terminal multiplexers have quietly shaped how we work:

Remote work is possible because sessions persist
DevOps exists partly because we can manage multiple servers
Pair programming evolved with shared sessions
The “always-on” culture thrives on persistent sessions
Configuration files became a form of self-expression

Confessions of a Multiplexer User

We all have our secrets:

That session running for 847 days that you’re afraid to close
The configuration line you copied but don’t understand
The time you lost an hour of work because you forgot to detach
Your shameful use of the mouse in copy mode
The guilt of using regular terminal windows sometimes
That one keybinding you can never remember

Final Verdicts

GNU Screen: ⭐⭐⭐⭐☆

The Verdict: Like a reliable old truck, it’s not pretty, but it’ll outlast everything else. Screen is the terminal multiplexer that refuses to die, and honestly, we respect that. It’s earned its place in the Unix hall of fame.

Best For: Ancient systems, minimal environments, multi-user collaboration, and people who think features peaked in 1995.

Tmux: ⭐⭐⭐⭐⭐

The Verdict: The terminal multiplexer we deserve in the 21st century. Tmux took everything good about Screen, fixed the annoying parts, and added features that actually make sense. It’s what happens when software evolves.

Best For: Modern development, complex workflows, people who like nice things, and anyone born after the fall of the Berlin Wall.

The Last Word

Here’s the secret that nine chapters have been building to: it doesn’t really matter which one you choose. Both Screen and Tmux solve the fundamental problem of terminal session management brilliantly. The religious wars between them are mostly academic.

What matters is that you’re using a terminal multiplexer at all. You’ve joined an elite club of command-line users who:

Never lose work to connection drops
Can leave work running overnight without worry
Understand the deep satisfaction of reattaching to a session
Have more terminal windows than they have life problems
Know the true meaning of persistence

Whether you choose the venerable Screen or the modern Tmux, you’re making the right choice. The wrong choice is using neither.

Parting Wisdom

As you venture forth with your chosen multiplexer, remember:

Your configuration will never be “done”
You’ll always find sessions you forgot about
The perfect keybinding setup doesn’t exist
Someone will always judge your choice
But your sessions will persist through it all

May your connections be stable, your sessions be persistent, and your prefix key be comfortable.

The Real Last Word

# Whichever you choose, the ending is the same:
$ exit
[screen is terminating]

# Or

[exited]

# But your work lives on, waiting for your return.
# And that's beautiful.

Acknowledgments

To Screen, for 37 years of faithful service. You’ve been there through thick clients and thin clients, through dial-up and fiber, through every evolution of the terminal. You’re the COBOL of terminal multiplexers, and we mean that with love.

To Tmux, for showing us that software can evolve, documentation can be readable, and features from this century are actually nice. You made terminal multiplexing cool again (was it ever cool?).

To all the forgotten sessions still running on servers worldwide: we see you, we appreciate you, and we’ll probably never clean you up.

And to you, dear reader, for making it through 10 chapters about terminal multiplexers. You’re either very dedicated or very bored. Either way, you’re now equipped to make an informed choice.

Choose wisely. Or don’t. Both tools are great.

The End

P.S. - Check for detached sessions before you close this book. You probably have at least three running somewhere.

P.P.S. - screen -ls or tmux ls. You know you want to.