Please Don't Promote Wayland
stoppromotingwayland.netlify.app
Please Don't Promote Wayland
1–10 of 90 posts
Re: Please Don't Promote Wayland
#2Missed opportunity for the (anonymous!) authors to demonstrate understanding about why some are promoting Wayland.
Re: Please Don't Promote Wayland
#3Only a casual user of Linux desktop computing but my experience with ui stability seems to have gotten much worse after switching to Wayland.
Re: Please Don't Promote Wayland
#4I am very open to Wayland in theory but I legit worry because it's been in the air for years and years and it still feels so far away. And some of the Wayland-y points around things like security just never felt relevant to me.
Though the real pain points for me have been around the various containerization things that just cause things like my IME to barely function.
At least Python 3 if you started your project on Python 3 you mostly could just get where you wanted to be.
Re: Please Don't Promote Wayland
#5I’m not a fan of Wayland or a detractor of X. I’m not personally invested in either of them. I couldn’t care less what’s pushing pixels at my screen as long as it works.
That said, what you need to know about Wayland is that the X.org devs mostly migrated to it en masse because they said X had hit an evolutionary dead end and couldn’t be dragged into the present, by the design of it. These were the people who were already maintaining X and presumably liked it. I doubt there were a lot of haters in that crowd.
It’s not like someone invented Wayland and shoved the X devs out of the way. The X devs largely became Wayland devs because they believe it’s the better path forward. I don’t really know how I could argue against them.
Re: Please Don't Promote Wayland
#6A lot of wild quotes here
> Training Overhead
> $5,000-$15,000 per IT staff member for multi-compositor environment training
When's the last time your IT department gave you "multi-compositor training"?
> Software Replacement
> $500-$2000 in software replacement costs when tools don't work under Wayland
> Multi-Monitor
> X11: Reliable, consistent behavior
> Wayland: Compositor-dependent, often buggy
> Distro wars intensified: Choice of display server becomes a major differentiator
Definitely written by AI
Re: Please Don't Promote Wayland
#7They're way too late now. The question is not about promotion anymore, just about when will the alternative to away. This page kinda made sense 2 years ago.
Re: Please Don't Promote Wayland
#8Without necessarily supporting or opposing the statements (because I have no opinion about Wayland after all), the first public mention of this website seems to be [1].
Re: Please Don't Promote Wayland
#9As much as X11 is an overly complex and dated protocol, this article hits its mark well. My current desktop is actually running Wayland, but I still need X11 for a variety of reasons.
I see the development advantages of Wayland, but not the practical advantage as a user. And even as a developer, X11 is stable and well known (albeit definitely weird in places).
At the end of the day, things worked perfectly on X11 and my audio and video and various apps still glitch a lot on Wayland even after all these years. Most of that is not exactly Wayland's fault, but it highlights the advantage of X11. It's the devil you know (and everyone has worked out a lot of edge cases for).
Re: Please Don't Promote Wayland
#10I am very open to Wayland in theory but I legit worry because it's been in the air for years and years and it still feels so far away. And some of the Wayland-y points around things like security just never felt relevant to me. Though the real pain points for me have been around the various containerization things that just cause things like my IME to barely function. At least Python 3 if you started your project on…
The IME problem was the only thing keeping me on "legacy" X11 a couple years ago. Is it still the same today?