← Sat, Oct 3 digest

Make Tmux the OS

read article ↗ hn thread ↗

A thought experiment on redesigning desktop operating systems around task-oriented, scrollable, tmux-like workspaces and AI-assisted layout management.

read it It offers a thoughtful, historically grounded critique of modern window management and proposes concrete architectural patterns for future desktop environments.

summary

The author examines why desktop operating systems remain stuck in outdated hardware metaphors and proposes a task-oriented interface inspired by tmux, tiling window managers, and historical research like Rooms. By combining infinite-canvas viewports, detachable browser tabs, and a constrained local LLM to handle layout organization, the system would eliminate manual configuration while preserving user context across display changes. Commenters debate whether existing tiling window managers or terminal multiplexers already solve these problems, with many noting that the main barrier is user-facing polish rather than missing primitives.

key points

  1. Modern window management still struggles with multi-monitor docks, private versus public views, and task switching, echoing human-computer interaction findings from twenty years ago.
  2. The proposed OS architecture features an infinite canvas viewport, task-scoped grouping, and deterministic reflows that handle display changes without collapsing layouts.
  3. A local LLM interface acts as a proposal engine via constrained tool use, allowing users to organize complex task states without editing configuration files.

who should read it

Software engineers, UI designers, and power users frustrated with conventional desktop window managers and multi-monitor workflows.

discussion positive

consensus

Commenters generally agree with the author's diagnosis of broken window management and filesystem silos, but many argue that existing tools like tiling window managers, Niri, or tmux already solve most of these pain points if users are willing to configure them.

pushback

Some commenters push back on the author's rejection of configuration files, arguing that power-user tools require explicit setup and that blaming operating systems ignores existing Linux and tiling window manager solutions.

best comment by kmarc ↗

I like articles that discuss out of ordinary approaches. This is one of those, and I relate to the pain the writer also has.

However...

> Different people use windows totally differently.

The older I get, the more impatient I am with this. In the industry, we normalized that high paid software developers (who are way better programmers, or infra people than I am) waste hundreds of engineering hours with their absolutely broken window management, and command-tab hell. Whenever I have to witness a screenshare of a colleague, my time is also wasted.

I wish this would be an interview gating: …

It argues that high-paid engineers waste massive amounts of time on sloppy window management and should treat workspace efficiency as a core professional skill rather than a UI novelty.

Generated by an LLM from the article and thread. Check the sources before relying on it.