I’ve been on Wayland for the past two years exclusively (Nvidia).
I thought it was okay for the most part but then I had to switch to an X session recently. The experience felt about the same. Out of curiosity, I played a couple of games and realized they worked much better. Steam doesn’t go nuts either.
Made me think maybe people aren’t actually adopting it that aggressively despite the constant coverage in the community. And that maybe I should just go back.
Message me on matrix if you want help setting all of that up, but waybar absolutely supports clicking tray icons.
You should switch if you value any of the following:
a. Any x11 client can record your screen without notifying you
b. Any x11 client can record all of your keystrokes without notifying you
a. Tighter integration with input/output configuration, which results in things like per-input settings are very difficult to do on X11, I have a mouse that only works on one screen and another mouse that works on all my screens, which makes it so that I can have my TV pointed away from my desktop and use a wireless mouse and never lose the position of my cursor while still keeping my other displays active, for example
b. You can’t modify mouse sensitivity on x11 (except in a hacky way with acceleration)
c. After switching to sway I just noticed so many hacks that I configured went away.
a. x11 can’t support monitors with mixed refresh rates because how it handles rendering is fundamentally flawed
b. on x11 most animations are fundamentally broken (try resizing) because of how rendering is handled, check out the animations on hyprland and how smooth they are, that’s not something that can be done on x11 for a low performance overhead
c. so many scaling problems, native wayland apps work perfectly in this regard nowadays.
Ok, because of this post - I decided to bite the bullet and try wayland again. And it was much better experience this time:
I’ve installed sway “pattern” on OpenSuse-Tumbleweed and:
I confused it with swaybar, that’s installed with sway by default and should be an i3bar-compatible. Waybar doesn’t seem to support i3bar protocol, but anyway, after I configured it - it’s like 95% there from what I want.