The issue with wayland is that both the process and the base mechanisms had significqnt flaws, that made it take a long time to get things working. In all fairness, the core team uad a valiant effort for a dwcade, hampered by unresponsive complainers, and late-to-the-party suggestions.

Fyi: I am an early WL adopter, but not on any of the major DEs.

Some people just can’t find a better hill to die on it seems.

The software you use working correctly is kind of a big deal, though.

Window manager automation. I use hotkeys to resize and move windows based on their title, pin them to certain monitors, etc…

ydotool is a step in the right direction, but AFAIK it can only simulate mouse and keyboard input

Protip: People who have iGPU + nvidia can just set the iGPU as main GPU on the BIOS and offload 3D programs to the nvidia via prime-run like they would on a laptop.

That’s my setup.

Guilty as charged

On my old nvidia laptop with Endeavouros i have some minor lag from time to time, nothing too crazy. But there are a couple of things i can’t make work. For start i can’t lower the gamma with xrandr, wlr-randr should work but my nvidia give me the middle finger. Secondly i can’t, for the love of me, find a decent onscreen keyboard app to use. I can technically enable the touchscreen keyboard in my desktop adding KWIN_IM_SHOW_ALWAYS=1 but is just too bothersome to have it pop-out everywhere. Also, while most of the app-images works, last time i’ve tried running this one https://github.com/ryzendew/Linux-Affinity-Installer it crashed 9 times out of 10. All of this works just fine on x11.

KDE on Wayland has only very recently started to become workable for me, before that it was utter crap as I switch between home and office with my laptop, with varying display setups. In that case you got stuff like screen positions not being remembered and applications consistently starting off screen, requiring gymnastics to coax them onto a display.

And regularly it would crap out and not show output to one of the displays, if you opened up display manager you’d see the displays not touching and a big red error telling you that gaps betweens displays aren’t supported. Well here’s a brilliant idea, how about not automatically putting a gap between them in that case?

As I said, last few months it works better (although I still encounter some issues from time to time that I never had on X11). But the whole Wayland protocol had such a rough start, with issues encountered often being downplayed by parts of the community because “it’s better and we don’t want to hear otherwise”, that I simply cannot feel any love for it anymore. There was too much basic stuff that took too long to support, while people were shouting “but HDR!”, “better code!”. I don’t fucking care, I just want to be able to work and for too long that required X11.

Edit: some typo’s and improved readability.

And the network transparency argument is long gone. While you can indeed network windows over the wire, most toolkits use client side rendering/decorations. So you’re just sending bloated pixmaps across the wire when things like RDP , VNC, etc deal better with compression, damage to the window, etc. And anything relying or accelerated with DRI3 is just NOT network transparent.

Most modern toolkits have moved past X11 because the X protocol was severely lacking, and there wasn’t a good way as a committee to modify the protocol in an unified manner. I mean look at the entire moving Earth that it took for XFixes and Damage extensions. Toolkits wanted deep access to the underlying hardware and so they would go out of their way to work around X, because it just could not keep up.

Running i3 on CachyOS and getting much better performance and stability.

My window manager (Am using awesome rn)

all of these have been fixed years ago.

I hear this all the time.

Yet when I bring up features that don’t work at all on X because it’s ancient, “no, thats superfluous. No one needs that.”

X was broken as fuck and held together by duct tape and zip ties, as long as no one looked at it wrong.

X is broken in many different ways. It has a huge codebase made to support a poor design that was optimized for machines 40 years ago. No one wants to touch the code base since it is so incredibly fragile plus the original developers are much older now.

In all fairness, it did work for way longer than anyone expected. I doubt the original designers of the X protocol anticipated it lasting this long.