Actual Window Manager May 2026

Your text editor draws to a hidden buffer. Your browser draws to another. The compositor steals both, layers them, and presents a photograph of windows to the display. When you drag a window, you are not moving the window—you are moving the photograph of a window, then asking the application to redraw its hidden canvas, then taking a new photograph.

The actual handoff is precise: the window manager routes the event to the correct process based on its internal map. But the map is always slightly out of date. Because your input arrives asynchronously—interrupts, device drivers, kernel queues, compositor scheduling—the window manager must guess which window is actually under the cursor at the moment of click, not when the event was recorded. actual window manager

Then came compositing. Now, each window draws to an off-screen buffer—a private canvas. The compositor (often merged with the window manager) then paints all these canvases together, adding shadows, transparency, and animations. Your text editor draws to a hidden buffer

The answer is stranger, more fragile, and more philosophical than you think. There is no such thing as an "actual window manager"—only a series of elaborate deceptions that, when woven together, become the single most intimate piece of software you never think about. Let us begin with a technical truth: your screen has no windows. When you drag a window, you are not

That is the miracle of the actual window manager. Not that it manages windows, but that it convinces you—every single day—that windows exist at all. End of piece.

Your operating system's core understands processes, memory pages, and file descriptors. It does not understand rectangles containing user interfaces. The "window manager" is a userspace fiction—a shared hallucination among applications, the compositor, and your eyes. So, after all this deconstruction, what is an actual window manager?