Byobu: screen with a coat of polish (and a status bar that saves)

Back in April, this blog described Screen as a terminal multiplexer : detach, reattach, never lose an ssh session. Six months later, byobu arrives and asks an impertinent question: if everyone configures the same Screen the same way (status, colors, shortcuts), why not ship the configuration ready-made?

That is exactly what byobu is: born in Ubuntu as screen-profiles, renamed byobu in 2009 (the Japanese word for decorative folding screens, an assumed wink), the tool wraps your existing Screen in a coat of polish without changing the engine.

What the polish brings

A status bar at the bottom of the terminal showing what admins stare at all day: CPU load, memory, disk, network, battery, apt notifications and updates. Each element toggles individually (F9 -> toggles) and the bar refreshes on its own.
Coherent F-key shortcuts: F2 new window, F3/F4 navigation, F5 profile reload, F6 detach, F7 copy mode, F8 rename, F9 configuration menu, F12 escape hatch. Done with C-a c that nobody ever memorized: laptop keyboards have those keys, might as well use them.
Zero migration: your Screen stays your Screen. byobu does not fork the protocol, it writes ~/.screenrc and status scripts in bash/python. Detach with byobu, reattach with Screen.

Why it is a good stepping stone

Byobu belongs to the tools that tell the truth about terminal software: the value is not in the engine, it is in the defaults. Screen had the engine since 1987 and a doc that scared people off; byobu took the engine and made the entry price one command (byobu, in Ubuntu 9.10, one apt install). For the busy admin, it is the delta between “I will configure screen tonight” and “I run byobu now”.

And tmux in all this?

tmux came out in 2007, two years before these lines and it fixes at the engine level what Screen had dragged since 1987: a real client-server model, clean pane splitting, a readable configuration. But in 2009 it is not yet everywhere, whereas byobu wraps the Screen every distribution already has. The two approaches do not actually oppose each other, because byobu is a presentation layer and not an engine: nothing prevents it from one day learning to sit on tmux rather than Screen and the day tmux is the default everywhere, that is probably what will happen, without my status bar noticing. In the meantime, for the admin who wants the comfort right now without rewriting a .screenrc, byobu remains the honest shortcut.