Comment Re:But they dropped X11 support (Score 5, Interesting) 33
Right, they refactored much of kwin to support wayland which was really laggy and generally sucky before 6. With the release of 6 they basically did the absolute minimum to keep x11 working during the refactors and that resulted in a lot of lag/etc bugs in x11. And for what the benchmarks show a tiny latency advantage now with wayland, but that advantage evaporates for ~90% of the applications running which are still using toolkits that in turn require Xwayland. And at the same time completely messed up things like damage updates, and a few other things one would generally consider optimizations for power/efficiency which would be huge hits if we weren't all running on multighz machines with fat GPUs. Its especially noticeable on network displays for example. The entire wayland architecture it runs out is a giant mistake for anyone who isn't a single task display (ex old ipad type use cases).
So, lazy or politics take your pick.
But, myself and a few other people have independently thrown, ML bots at the problem, some to simply resurrect the existing X11 support, by not breaking it for 6.8, and others like myself who have looked at actually doing something closer to a performance/correctness implementation that should exceed the core wayland code by leveraging X's advantages along with DRI/EGL/vulcan. So, don't be surprised it there are forks by people who are more interested in a stable DE, rather than playing political games like removing the ability to independently control the title bar color from the GUI, or having too use global scaling... And unlike a lot of "reimplementation" plans this has much of the existing code to work with, so its more a proper cleanup with appropriate tests to assure the bots aren't making a larger mess.