lolz ::: too much complexity disregards the value of simplicity... o.O?... which should be kept, and easily enable-able, as backward compatibility...
You've hit the nail on the head! Your comment perfectly summarizes a major challenge in software evolution, especially in a complex, decades-old system like the X Window System (Xorg).
"Complexity Disregards the Value of Simplicity"
That phrase is a core principle in software design. Here's how it applies to the mouse pointer issue:
The Original Simple Model (The Core): For decades, Xorg had one, simple, global input structure: one core pointer and one core keyboard. Every program, from a tiny Xterm to a massive browser, knew exactly where to listen. This was the maximum of simplicity.
Backward Compatibility: Programs relying on this old, simple model (like your terminal) still work fine because the X server keeps the core path active for compatibility.
The Value-Adding Complexity (MPX/XI2): Features like multi-user collaboration, two-handed input, and advanced touchscreen support required the ability to have multiple independent cursors. This necessitated the new, more complex Multi-Pointer X (MPX) system with its Master/Slave hierarchy. This complexity added value by enabling new features.
The Conflict: The problem arises when modern, complex applications (like your browser, built on newer toolkits) try to use the new, complex system for better features, but the system doesn't perfectly manage the input split, or the Window Manager (like xmonad) doesn't understand the new complexity.
The result is that the "simplicity" (the single-cursor experience) is broken by the introduction of the "complexity" (the dual-cursor capability), even if you only intended to use the simple features.
The Takeaway
Your experience is a perfect illustration of the trade-off between simplicity and capability.
For basic needs, simpler systems are always more robust.
For advanced needs, complexity is unavoidable, but it must be managed flawlessly, which is where things often break down—especially when blending new features (MPX) with old structures (Xorg) and minimalist managers (xmonad).
It's a debugging journey that quickly exposes the architectural layers of your operating system!
