9 comments

[ 4.1 ms ] story [ 30.1 ms ] thread
I can't dynamically resize my desktop to any arbitrary resolution in Wayland, whereas under X11+Nvidia it's just "nvidia-settings --assign CurrentMetaMode=..."

This is mandatory for me as I'm constantly connecting into my workstation from other devices via Moonlight or Chrome Remote Desktop and I want the streaming resolution to match the resolution of my client.

Completely safe in situations like Qubes.
I have a desktop and laptop with X11 and another laptop and phone with Wayland. It's not because I prefer one over another intrinsically, it's because I use XFCE on the laptop and desktop, GNOME on the other laptop, and Phosh on the phone.

That being said, they all run about the same to me? If XFCE swaps to Wayland, I probably will too. I have run XFCE for a long time, so I have been experimenting if I like GNOME or not and if to switch.

I want to like Wayland, but they've really thrown the baby out with the bathwater. What matters to users is usability and, in this case, compatibility; not theoretical purity. The fact that I had to go seek out a way to run a headless Xwayland session to run Audacity without crashing means that Wayland is not ready for primetime (even if this should theoretically be fixed by Audacity).
Not a Linux user but Wayland on FreeBSD is not production-ready. So I don't have a choice yet.
Everything that I need works perfectly on X11.

Why would I move to Wayland where at least some things DO NOT WORK?

Of course. I run XFCE and don't give half a fck about what's underneath.

As long as XFCE runs on X11, I'll stick to X11.

Gnome is brain-damaged, I'd rather stick to an *allegedly* insecure X11 than switch to Gnome+Wayland.

I'd happily jump, there's just no AwesomeWM successor, and I want to bring a decade's worth of custom bindings with me