We are still fixing stuff in Wayland, stuff that Microsoft and Apple had figured out 20 years ago.
So defeating.
So defeating.
I don't know, given that the UX situation in Windows UI - itself a inconsistent disaster that makes the disjointed things that make up KDE looks like a consistent desktop experience. They can't decide what UI framework to keep supporting, they keep changing what you're supposed to use to build your GUI every bunch of years.
As for the Apple side, well, destroying everything every few years with almost no regards for backwards compatibility isn't "figured out 20 years ago".
On Windows not all Apps do scale on a HiDPI display. You then have to fiddle in the program's launch options and hope it's not too blurry when scaled.
Wayland does only have blurriness with certain Xwayland embeddings.
It's not a solved problem.
MS does a lot of things wrong, but backwards compatibility is still their strong point.
Tangible benefits of switching to Wayland. And by those, I don't mean "no screen tearing", since it practically did not exist on most desktop environments with half-decent compositors.
> half-decent compositors.
At which point there was no point of X11 middle-maning between the compositor and apps -> tada Wayland it is.
Also, screen tearing is a bigger issue on bigger resolution higher refresh rate monitors, hardware just grew up to 1080@60fps.
Chrome, for an example. Firefox isn't much better.
And no one ever said that every program will have to move to Wayland, XWayland was created specifically for legacy applications to be usable that won’t port over. (Though their number is limited, since most applications use a framework like gtk/qt/electron whatever and all of those natively support wayland without changing the programs).
Wayland means - for me - no fiddling with text files if I want an external monitor, roatated, with a weird resolution.
As far as I understand it had sync issues even on single monitor setups until relatively recently because it did not try to sync at all and instead just refreshed everything based on an internal timer.
For what it’s worth didn’t matter compositing is on or not.
To be honest the situations where I needed tearing free output on multiple displays I usually ended up configuring separate X screens.