> Wayland aside, which is going to be a disaster and neuter the Linux desktop
I can't recall where I said this some time ago but I feel like between all the FOSS "wars" (KDE vs GNOME, Vim vs Emacs, Ubuntu vs everyone else...) X11 vs Wayland is the most toxic of them all. It feels to me Wayland haters are the most noisy. For most people like me who are being using Wayland for years it is absolutely great right now so we can't complain. I'd go as far as to say people having issues with Wayland are having mostly a me problem rather than a Wayland problem - yes, it can't be absolutely perfect, but it is a mamooth of a project and if you want it to be better you can help in a lot of ways, not just coding.
Plus, blog posts like this are of little to no help at all about that "Wayland is going to be a disaster and neuter the Linux desktop", maybe even contributing to it - I can't help but feel for the KDE devs who nowadays seem to be really open to new ideas and feedback from users (everywhere from Reddit to the bugzilla tracker and their discourse instance), but some guy decides to make a blog post and torch the whole project.
They typically make mountains out of minor gripes with Wayland while completely ignoring the huge gaping holes in X11 that made Wayland necessary to begin with. You cannot give normal users a DE that lets any random application have complete control over all of your desktop applications. Sure, it is fine to say, "I am not a normal user, so don't push Wayland on me until it fixes my gripes," but because the author is not a normal user, he should not be using distros intended for normal users. That's on him.
Adding a permission system was a huge improvement. Not actually bothering to implement useful features, even behind permission gates, is not an improvement.
What useful features aren't they bothering to implement? The author's complaint is about window positioning, but that is correctly a compositor feature, and his chosen compositor hasn't implemented it yet. https://bugs.kde.org/show_bug.cgi?id=15329
> For most people like me who are being using Wayland for years it is absolutely great right now so we can't complain. I'd go as far as to say people having issues with Wayland are having mostly a me problem rather than a Wayland problem
I mean, the article lists what appear to be bugs/regressions in the software. If the equivalent Wayland session is blurry and uses more CPU+GPU, that's not the user's fault.
I can't recall where I said this some time ago but I feel like between all the FOSS "wars" (KDE vs GNOME, Vim vs Emacs, Ubuntu vs everyone else...) X11 vs Wayland is the most toxic of them all. It feels to me Wayland haters are the most noisy. For most people like me who are being using Wayland for years it is absolutely great right now so we can't complain. I'd go as far as to say people having issues with Wayland are having mostly a me problem rather than a Wayland problem - yes, it can't be absolutely perfect, but it is a mamooth of a project and if you want it to be better you can help in a lot of ways, not just coding.
Plus, blog posts like this are of little to no help at all about that "Wayland is going to be a disaster and neuter the Linux desktop", maybe even contributing to it - I can't help but feel for the KDE devs who nowadays seem to be really open to new ideas and feedback from users (everywhere from Reddit to the bugzilla tracker and their discourse instance), but some guy decides to make a blog post and torch the whole project.