The biggest thing I can think of is that X11 is more flexible when it comes to specifying custom resolutions; which some people use to output 240p on CRT TVs for emulation. AFAIK, there is currently no real equivalent for xrandr on any Wayland compositor.
I’ve also noticed that Grsync’s password prompt is broken on Wayland. Thankfully, it has a feature that lets you preview the command it’s about to run, so that you can copy and paste it into a terminal.
Being a KDE user on EndeavourOS, I use Wayland everyday. I switched over a few years ago for Waydroid, but now X11 isn’t even an option for me with the current release of KDE.
Just looking at these comments, and the fact that wayland still isn’t as good as x11 after all these years (10, 15?) And all this budget shows that wayland is architectually wrong and will never be actually good.
Any software engineer will understand this. If your project is still in basically beta after more than a decade and that much budget, and it’s only selling point is that “but it’s slightly better than the decades old legacy system”, that project has been architectually wrong, and also definitely has awful management, and you call it failed.
I was sold when I could setup my 1440p@144Hz horizontal monitor and 4k@60Hz vertical monitor in Wayland without any issues. This was after hours trying to get it to work with X11 (and giving up).
The rest of your comment reads like ragebait, tbh. What, exactly, isn’t as good? What indicates it’s still in beta? What are the flaws? That was the whole point of the post, and “it has problems trust me” is not very helpful.
read the rest of the comments for that.
it’s still very unpolished and fragmented from my experience.
down voted for telling the truth. I use Wayland on my laptop and it works fine, but x11 is honestly still the defacto window system
I have to use x11 on my desktop (yes Nvidia) and it’s a nightmare. I try it every now and then though
Have you ever considered a career in set theory?