3 ms·
OK so I see that I didn't appreciate the complexity here. So even a "trivial" compositor like xcompmgr, that runs alongside a WM, has to do all of this dance?
by rollcat 2y ago
OK so I see that I didn't appreciate the complexity here.
So even a "trivial" compositor like xcompmgr, that runs alongside a WM, has to do all of this dance? The WM still has the authority to tell X, "draw this window here", but X lets xcompmgr take the wheel? (I can tell from here why X was already becoming more of a drag.)
- ChocolateGod 2y agoYeh and because compositors had to pull from X and push again, it added additional latency and work (having to copy around buffers). Wayland (as an API) was designed to solve, which is why in theory it's supposed to have better performance, latency and power efficiency, although it hasn't worked out great in all cases.