Unless you are on NVidia or need X11 specific things (E.g. a lot of the accessability stuff) I would go for Wayland, it still has some issues but so dose X11 and Wayland is simply the new display server from the xorg foundation because X11 was impossible to properly update by now, it has far too much lagacy code and didn’t get any new version in ages for that reason.
Wayland is not a display server, it’s just a protocol. The compositor acts as both window manager and handles the graphics card interface.
Wayland if you have more that one monitor. X11 can support multiple monitors but it is a disaster.
Rustdesk doesn’t work on Wayland and that is a real bummer
I run a dual monitor on X11 and never understood why people have issues with it? I’m by no means a Linux expert and I do run in Nvidia, I run different refresh rates. Can someone explain it to me?
I do similar. For laptops and docks, especially if they change setups it can be a pita (though you just need to copy files around).
Also the DE monitor config (ie that you use to login) is logically different to a users x config. So you gotta copy that over to make sure the primary monitor etc is right.
If your monitors are different DPIs then multimonitor X11 is awful.
If you’re questioning why anyone would have monitors with different DPIs remember that laptops exist.
I run 2 monitors with different DPIs and X11 works without an issue. Can’t say the same about wayland where scaling still has so many bugs it’s just unusable.
You can’t set 2 different DPIs for the monitors on X11. On one monitor everything is just going to be bigger than the other. Depending on the DPI difference it can be basically unusable.
You can configure software rescaling using xrandr and some scripts… But that can cause a massive amount of jank with anything that requires a degree of pixel accuracy
Valid point. I forgot about 4K… I run just 125% scale so it doesn’t bother me at all. Well it’s kinda funny that both protocols are broken in that regard.
I feel like taht’s often the case but Wayland as the newer protocol usually has the correct architecture with a early implementation while X11 has hard to fix architectural problems. I am a opponend of “whatever works for you” and I think that will be Wayland for most people fairly soon if it isn’t already but in case it actually isn’t I wouldn’t recommend it because, well, it doesn’t work properly for you.
Even without considering laptops, I can already imagine quite a few circumstances where someone might want monitors of differing DPIs. I’ve actually thought sometimes of getting a smaller monitor I can have off to the side that I display a browser window containing mostly text on when I’m playing videogames or working in something like Blender or Aseprite; yknow, for referencing a guide, wiki, or manual or something. I don’t even have a super high desire for a multi-monitor setup outside of that.
x11
2 monitors 144hz, 1 TV 120hz.
Nothing on any monitor can render at higher than 120hz
Play movie on any one screen, other screens can’t render anything at higher than 24fps
Wayland works fine
Wayland, because it’s faster, more stable, handles multi-monitor better, you can have animations while playing a game, no tearing, no fcking around window managers/compositors or shit, lower memory usage and 1:1 touchpad gestures
you have the same with X11… i have all these feats with my intel and AMD GPU.
So why Wayland then? Better architecture/codebase and more manpower. And I think it supports multi-gpu better, not sure as nvidia doesn’t play well with Wayland, it would be astonish that Optimus works any better.
Try running multiple monitors with different resolutions or gaming… Just in general (no seriously, people who think that gaming on X11 is better than wayland are fcking insane… No tearing, having to disable compositor to get more than 20fps, just works) in X, bet you’ll have a great time. And yes, Nvidia is the only reason why imo anyone should still be using X (if they don’t wanna use gnome)
Wayland for better multimonitor support, scaling, and tear-free rendering.
X11 because KDE cut some features for Wayland (some that will be cut in Plasma 6 X11 too, yay) and some apps just don’t support wayland for technical reasons.
Wayland, because anything I want to do is possible with wlroots compositors like sway. And if you don’t need a feature not yet implemented in wayland (e.g. screen tearing), wayland is usually the better experience.
Obviously switching from X11 to a standalone Wayland compositor like sway involves changing out some apps, it’s a core component of your system afterall. But xrandr has it’s wayland alternatives, rofi has lbonn’s fork with wayland support, dmenu has it’s equivalent, etc. The X11 tools might work, but usually aren’t as good of a experience (e.g. rofi X11 might stay in the foreground while not being able to react to keypresses, rofi-wayland fixes this.).
And I really like to try new things and be at the edge off new technology, so I really wanted to use wayland (And have been using it for years at this point).
Wayland. I’m quite happy not to have to delve into xorg.conf for my keyboard layout.
I use Wayland because of my multi monitor setup not playing nice otherwise.
For most users, it doesn’t matter. Just go with whatever your preferred DE uses. I love Hyprland, which uses Wayland, so I use that. I also like bspwm, so I would also use Xorg for that.
Wayland has a few issues still. I have issues with zoom lately, for example. Share screen also has trouble sometimes.
Wayland, security
X11, because it’s stable.
Wayland! When xfce comes with Wayland? When Linux Mint have wayland? #linuxmint #wayland
Hopefully not until it has full feature parity with X11.
X11 because my current setup on Wayland crashes constantly, otherwise always Wayland.
If Wayland works well enough for you, Wayland. If it doesn’t work, X11
I would refer you to this: https://www.youtube.com/watch?v=UW3nYiK3nd0
Wayland. It generally works a bit better at this point, and it will only continue improving while X11 falls behind. I occasionally need to switch back to X.org for some legacy screen-casting or remote desktop apps, but even the ones that support Linux as an afterthought are starting to add beta Wayland support.
