Wayland

“And one implementation that everyone settled on, and pretty much everyone can assume to be present is worse than multiple incompatible implementations how?”

“the community got constantly browbeat with 'this is the future' and 'it's so much faster!' when recent benchmarks have proven that to be false”

“A design that requires everyone to implement their own protocols and everyone to refix the same bugs in their own compositor is inherintly bad.”

“they seem very concerned about security and make screen sharing very complex now if you stray from the accepted path”

“Both systemd and wayland were quite broken when they were first being pushed onto everyone... they're mostly fine now.”

“Wayland either never had or has only very recently gotten support for applications that need to place their windows at application-commanded locations”

“having those same capabilities implemented piecemeal and incompatibly by five (and counting!) compositor ecosystems”

“It still lacks keyboard LED control, so unprivileged X11 programs that use the Scroll Lock light as an indicator cannot be ported to Wayland.”

“issues that people kept having under X, resulting in LOADS of bug reports, have more or less vanished now during wayland”

“HDR support, high bitdepth, per-screen refreshrate/scaling, and all those things are just "no apparant advantage" to you.”

“it may have got a bad name by being rolled out by distros (especially as the default) before it was ready for most users”

“The whole problem with wayland is this mistaken absurd belief that the security standards of a desktop are equivalent to those of a website.”

“The only understandable complaint is that wayland makes it hard for different windows to interact with one another for security.”

“to me it seems to work fine and X11 did seem to be carrying a lot of legacy baggage so a renew seems like a good idea”

“The problem is old (and even not so old) apps don't expose those APIs so interactions like UI automation on Wayland is limited, if not impossible.”

“I don't mind using Wayland these days, but I do feel most of the security arguments are aimed at the government/corporate/big server audiences”

“I use Wayland exclusively everyday and I screen record with OBS on both KDE and GNOME on multiple machines with no issues”

“Wayland was correct in first focusing on replacing this interface. The problem is the effort stopped there and left the ecosystem to figure out the implementation part.”

“On my Wayland desktop, copy and paste works fine, window previews work fine, OBS screen capture works fine.”

“accessibility tools which need access to everything X gave them are never going to be compatible without being completely rewritten with Wayland in mind”

“It's hard for me to even explain some of the bugs I saw with X that disappeared overnight when I switched to Wayland.”

“Ever since Wayland added support for changing mouse scroll speed & changing/customizing middle click behavior that is a lot more consistent”

“And this is the inherent problem with Wayland. Now we have to deal with a combinatorial explosion of things to try to get something that "just works."”

“It is many years, I guess close to a decade, since I needed to change X config manually. I still find the odd rough edge in Wayland”

“Turns out: absolutely no problem. The tooling around Wayland and adjacent programs is way more modern and functional.”

“HDR support, 10/12bit colors, displays with different dpi/refresh rate etc is just not really an obvious benefit to you?”

“this GPU (Radeon VII) crashes regularly under X11 nearly every time I open a new window, but is perfectly stable under wayland”

“Moving complexity from the layer you only have one of, to the layers where there are many, many competing pieces of software, was an absolutely bonkers decision.”

“My big use case that Wayland enabled was being able to dock my laptop and seamlessly switching apps between displays with different scale factors.”

“Inclusion of new protocols in the stable release requires existing, proven implementations and consensus across multiple implementors”

“Out of the box I used have more problem with X11 (tearing and font rendering being the most annoyingly common ones)”

“as far as I can tell the available remoting solutions still cannot enable a headless LXC container to serve a KDE Plasma Wayland desktop”

“replacements seem dead or ineffective or incomplete - that is quite frustrating for something that was aggressively advertised as "this is now the future"”

“having fucktons of incompatible compositors because wayland, by design, does not want to standardize things they decided would be harmful”

“There's no cross platform way to do that with Wayland because ""security"" means it's supposedly dangerous for programs to read the title bars of other applications”

“it's really frustrating when people feel this rush to move off the old way that's working in favor of a new way that doesn't yet do everything the old one does”

“I've been using wayland on three computers for the last two or three years and haven't had a crash that could be attributed to wayland”

“I have used a Wayland only system for a long time and application-level crashes certainly don't bring down other applications”

“Wayland is improving, but there is still a difference between what the spec supports and what developers can rely on”

“Wayland ensures everyone has a voice because it's an open protocol which means discussion and development are done in the public.”