Actual Window Manager — Limited

Understanding that it is a construct—a set of compromises between performance, policy, and physics—can make you a better user. When a window lags, you will know: the compositor missed a frame. When focus jumps unexpectedly, you will know: the policy engine made a choice you did not intend.

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

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. Understanding that it is a construct—a set of

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 actual handoff is precise: the window manager

But have you ever stopped to ask: what is an actual window manager?