Actual Window Manager __full__ May 2026

The window manager is the cartographer of this empty territory. It draws lines where none exist, declaring: "From pixel 320 to pixel 960, this region belongs to Firefox. From pixel 0 to pixel 320, this region belongs to your terminal."

At this level, there are no windows. There are buffer objects, page flips, and scanout engines. The window manager is a ghost in this machine—a high-level construct that the kernel does not recognize. actual window manager

Who made that cursor appear? Not the terminal emulator—it has no idea your mouse has entered. The window manager did. It noticed the mouse crossing a boundary, sent a WM_MOUSEENTER event (or the Wayland/X11 equivalent), and the terminal responded by changing its cursor. The window manager is the cartographer of this

Physically, your monitor is a grid of pixels—millions of tiny lights turning on and off. The graphics card sends a frame buffer: a rectangular array of RGB values. That buffer has no concept of a "window." It has no concept of a "taskbar," a "close button," or a "border." There are buffer objects, page flips, and scanout engines

Now move the mouse to a text field in your browser. Click again. This time, the browser receives the click, moves its own cursor, and starts blinking.

Here is the unsettling part: in a composited system, no window ever touches the screen.