Terminal borders that don't cost a cell
Terminal developers are experimenting with “cell borders” – decorative lines drawn around text that don’t consume character cells – to make text-based user interfaces (TUIs) denser and more visually refined. Commenters are split between excitement over richer layouts, better handling of things like tables and markdown, and concern that this pushes terminals toward becoming lightweight, incompatible web browsers instead of simple, composable tools. Much of the debate centers on whether to extend existing terminal protocols versus adopting higher-level or graphical alternatives (HTML over SSH, X11/Wayland-style remoting, or new semantic UI protocols) that might solve the same problems more cleanly.
Aesthetics and UX of Cell-Free Borders
- Some like the visual polish, tighter boxes, and ability to draw borders through graphs and tables without losing content cells.
- Others prefer “breathing room” around borders; worry about crowded, noisy UIs where every element is boxed.
- Discussion around “useless gaps”: gaps between panes help disambiguate windows, but gaps at monitor edges are seen as visually redundant.
- Rounded corners and filled interiors are appreciated by some, but noted as harder with certain alternative techniques (e.g., overstrike).
Terminals vs GUIs/Browsers
- One camp wants a purpose-built, information-dense, monospaced UI framework or even a new semantic protocol above the cell grid (better for accessibility, scrollback, structured data).
- Another camp insists terminals’ value is precisely their simplicity and constraints; richer UIs should use GUI toolkits (Qt/GTK), X11/Wayland, or HTML/JS.
- Serving HTML over SSH is proposed; critics call HTML itself a pile of legacy hacks and prefer cleaner, higher-level GUI protocols.
- Concerns that terminals are slowly turning into lightweight browsers; some see this as inevitable, others as feature creep.
Technical Mechanisms and Alternatives
- Cell borders as a new per-cell property are contrasted with:
- Overstrike mode (DECSET 20) to draw borders over text.
- Unicode “border diacritics” as composable line glyphs.
- Vector or pixel-level protocols (Tek4010, generic graphics protocols, remote GUI channels over SSH).
- Debate over whether overstrike is an elegant minimal fix or too limited compared to cell borders’ richer feature set.
Compatibility, Multiplexers, and CJK
- Multiplexers like tmux may drop unknown DCS sequences; CSI-based approaches might interop better.
- Extra per-cell state complicates storing, redrawing, and edge cases in multiplexers and terminals.
- CJK width issues: box-drawing characters are East Asian–ambiguous; in double-width configurations, ASCII-style frames misalign.
- With cell borders, misalignment can appear as lines stopping short when terminals and apps disagree on grapheme width; how borders attach (to cells vs grapheme clusters) is flagged as an open design question.
Performance, Philosophy, and AI
- Some worry modern TUIs may redraw at high frame rates and consume RAM, eroding the traditional “lightweight TUI” advantage.
- Others point out that borders themselves don’t force inefficient redraw patterns.
- Several commenters dislike “AI hustle” tone and phrasing, but others appreciate explicit AI-use disclosure and judge the work on its merits.