Why KDE's KWin Doesn't Integrate Weston/QtCompositor For Wayland Support

KDE developers have been porting their Plasma 5 + KDE Frameworks 5 stack over to Wayland, but at this point it's not nearly as mature as the GNOME Wayland support. As such, KDE developers have to fend off questions from time-to-time why they don't "just integrate QtCompositor" or the Weston library for speeding up their efforts.

KWin maintainer Martin Gräßlin has written a new blog post today to address the matter why KWin doesn't integrate QtCompositor or libweston for speeding up their Wayland support. Martin's post covers the KWin compositing model and then specifically why QtCompositor and Weston aren't used. Using QtCompositor would mean losing a lot of KWin's features right now and still needing to write a lot of code. Meanwhile, libweston really isn't tailored for KDE's purposes.

Those interested in finding out more can read Martin's blog post with all of his commentary.