Perhaps X.org should sue Elon Musk over the whole X thing. Then when they win the lawsuit, use the money to build an even better X.org that rivals Wayland.
Switch from gentoo to fedora recently and use wayland as the default with nvidia
Everythings works fine until i fire up some games. All the games have this weird screen flickering and screen tearing which render a black box and literally unplayable. Tried rebooting, upgrading, downgrading and no avail.
If you're on KDE Plasma 6, there's an option to enable screen tearing in fullscreen applications, turning that on seems to have fixed a similar problem I had.
This has been an issue since NVIDIA introduced alternating frames in the 545 driver. To fix this, explicit sync was recently merged into the Wayland protocol, now all it needs is the merge into Xwayland and the new NVIDIA driver that supports it, which is rumored to be released as a beta around May 15.
Until then, you either have to game on Xorg or use the 535 driver.
Thats another reason i switch from gentoo to fedora. I do learned a lot from gentoo, but sometimes its just tiring to build everything and i just want something that works
Well, i used to be a gentoo user for 2 years or more. But after a while, it kinda bothersome to compile everything on my current pc. So i switched to fedora and its been great :D
Sorry if i didnt get your point, english is not my first langauge
Not tools like screenshots, screen recording - because Wayland is inherently different, you couldn't make those work in Xwayland without sacrifices.
I think Wayland is in a good enough state to be a daily driver for most (non-NVidia) users, but there's still big caveats to keep in mind that can be deal breakers.
I was talking about xorg specific tooling. For example sxhkd doesn't work in wayland. Swhkd is the wayland alternative that should work in both, but the last release was 2 years ago, is only available through AUR, and when I compiled it, it didn't work with either Wayland or xorg.
There isn't such thing as a WM under Wayland. There are only compositors which make up everything such as the WM, Effects compositor, io etc.
To standardize things for smaller compositors things like wlroots exist. Creating a basic compositor using that is around 100 lines of code
Yeah, and that was my point: Wayland turns DEs into inflexible monoliths. You trade modularity, customisability, and stability for better scaling, high-end monitor support, and theoretical security.
The theoretical security part is what got me "huh 🤨" as well... like "ok, but all of this is planned... or in the works... or it should work... when does the "it does work" part kick in 🤨".
Switched to Wayland recently. Went to go play MechWarrior 5 with some friends and my mouse didn't work properly in the game. Switched back to Xorg. No more problems.
As someone who was completely ignorant to x and wayland until recently, my only experience is my distro having a wayland and x combobox during login, and random things not working when I switch it to wayland. The only reason I know this option even exists is because wayland was on by default and random stuff didn't work. I'll happily switch to the new better tech once it stops breaking stuff like KDE Connect and random games.
I use an app on my phone that lets me use it as a touchscreen and keyboard for my Linux media PC. I have no idea if it will ever (be able to) support Wayland.
Wayland is maintained by the same people who made X.org. If you like X.org maybe you could volunteer your time to do maintenance on it. No one wants to touch a dead codebase.
Screen color calibration, no nvidia support (not their fault, but that doesn't solve the problem, does it), HDR (KDE has it in beta, but no one else does)...
I'm sorry, it's an unfinished product (unlike, let's say PipeWire, which is why it was quickly addopted). X.org devs went 180 regarding development of Wayland vs X.org. It had a bad foundation to begin with, not enough supported protocols... everything after that is just patching the obvious.
They should have ditched Wayland 15 years ago and start from scratch when they saw how poor the standard was regarding protocols. If X.org was too big and heavy, Wayland went in the complete opposite direction. A middle ground should have been made, and adoption would have been quicker and more stable.
I love Wayland but I don’t love half my apps rendering as blurry when using my HiDPI screen. Wayland treating me good so far. I wanted to ride the poo poo on xorg train cause of Wayland’s snappiness and being modern but functionality is everything.
