Oh, about 4 or 6 months ago? I had problems with font scaling and multiple monitors with different resolutions, and correct DPI handling. I hear that's all been fixed, but I haven't tried it yet.

I have no reason to try it. X works just fine for me. I have herbstluftwm set up the way I like it, and there's only one Wayland window manager that looks at all similar in functionality to herbstluftwm (niri?). picom gives me all of the functionlity I find useful or attractive: dimming non-focused windows and light tranparency on terminals. Switching would be a lot of work, finding a bar to work like polybar, getting the WM set up, finding a good terminal to replace rio. And why? For what? X works well and reliably, and I don't have any edge cases like I did in Wayland, so should I make the time and effort to switch? There's no compelling reason, at the moment. There's nothing I want, or need, from Wayland.

I'll probably log in to Niri to play with it one of these days when I have nothing better to do. I'm curious if it does anything herbstluftwm doesn't.

Eventually, I may be forced to switch, but at the moment I just see a bunch of unnecessary effort on my part to just get back to what I have under X now. Seriously, what's the compelling reason for me to use Wayland?

I bought an AMD gpu to use sway, I feel like the fuckers owe me 50 usd now which is what I payed for the gpu.

https://github.com/swaywm/sway/issues/8000

https://github.com/swaywm/sway/issues/8001

https://github.com/swaywm/sway/issues/8002

https://github.com/swaywm/sway/issues/8191

And it's devs are not willing to fix the most basic issues like correctly handing a fucking environment variable lmao

https://github.com/swaywm/sway/pull/7380#issuecomment-2453356422

Not to mention I have a different issue that I haven't even bothered to report because I already know won't be implemented:

I have 3 displays that right now I use xrandr to merge the 3 displays into one, this is not possible in any wayland compositor today, the closest thing I found was someone suggesting to use gamescope to make a window with the resolution of the 3 displays but that's a hack and doesn't work for me because I need the displays to be merged, not just span a single window across them.

There is also no universal xdotool or similar in wayland to query info about windows, so you have to learn to use the CLI tool provided by each DE/WM and then handle the data, which in the case of sway it is json formatted.

So what used to be a simple xdotool <args> | grep became needlessly overcomplicated and different for each wayland DE/WM.

No, never. I mean, sincerely I can't remember ever owning an NVidia GPU.

For years, my main daily driver was a laptop which had an Intel GPU. When I swiched back to mostly a desktop a couple years ago, I went with AMDs -- because I think they make better CPUs than Intel -- and so am running Ryzen GPUs on the two desktop computers. All of the other computers in my house are headless micro-servers, ODroids, mainly.

Both the Intel i915 and the current Ryzens are rock-solid and fast under X. I haven't had issues on Intel GPUs in years, and have never had to do any tweaking on Ryzen. Back in the early days of my XPSes (I've owned 3 models over the years) I used to have to muck around with the drivers, but not in the past 6 years. A couple years ago I installed Artix on the XPS and didn't have to do anything with the drivers or X config -- it just worked. Earlier this year I wiped Artix and installed EndeavourOS, and again, X worked and has been utterly solid without any tweaks.

I am aware that some people have issues with X -- there's this tearing thing I've read about, but I have never, in all the decades I've been running Linux, seen it myself. Even back when I was editing modlines and xorg.conf. In all those years I've seen a lot of issues with X -- missing drivers, poor GL performance, difficult configuration -- but never that tearing thing. I can imagine if I did, I'd be glad for a solution, and would be eager to switch.