4 ms·
It's not just stakeholders, it's because instead of one Xorg doing everything, each compositor now has to implement similar things. So efforts are spread across
by shmerl 6y ago
It's not just stakeholders, it's because instead of one Xorg doing everything, each compositor now has to implement similar things. So efforts are spread across all existing compositors instead of being concentrated. That slowed down progress tremendously.
I'm all for Wayland transition, but things could benefit from concentrated efforts for sure.
- canofbars 6y agoI think the project wlroots exists to make it easy to just import wayland support so each DE/WM doesn't have to implement it.
- shmerl 6y agoIt exists and its idea is good, but major compositors aren't using it, so the benefit is lost in result.
- canofbars 6y agoThe major compositors don't seem to be having issues managing their own implementations so I don't see the issue. wlroots seems like the ideal tool for building your own DE/WM
- shmerl 6y agoNot sure how you don't see any issues. I explicitly mentioned several ones in the other comment.
- zanny 6y agoThey went that way for a reason, though. All the Xorg window managers (Mutter, KWin, etc) largely became behemoth projects in their own right to fill holes in X that could not be easily fixed universally. Since those projects were already faux display managers the X devs that started Wayland wanted to avoid that duplication again.
- shmerl 6y agoI get the reason, but it doesn't help that spreading of the effort slowed down the progress almost to a crawl. There is still no adaptive sync in KWin on Wayland and it's not going to appear soon as far as I understand.