I’m here to stay.
- 3 Posts
- 2 Comments
In short, X11 is a bit unsecure in its concept (like every program can read keyboard inputs you are doing right now). The multi monitor configuration possibilities and mixing different setups is basically impossible (I mean stuff like mixing 4k@120 Hz with G-Sync and another one with 1080p@60 Hz with just V-Sync). X11 or XOrg has a long history since the 80s with many versions, the code base is spaghetti code and its not a pleasure for developers to work on.
Wayland is new, with a fresh and modern code base. It eliminates the security and monitor issues. Programs not written for Wayland does not work, but luckily there is XWayland, which allows running X11 games on Wayland. You can think of like Proton for X11, but without the benefits of Wayland, just a compatibility mode. In Wayland there are sub protocols, meaning standard definitions, that are developed and added after some time passes. I personally think protocols being like an addon that allows doing more stuff in a standardized way across all systems that support it. Developers in Wayland have a much better time working with its modern code base.
Have a look at https://wayland.freedesktop.org/docs/html/ch03.html .
Looks like XDG Desktop Portal is using dbus and expects it: https://flatpak.github.io/xdg-desktop-portal/docs/common-conventions.html
And for the one user in your link https://snoo.habedieeh.re/r/voidlinux/comments/1471jbk/why_do_i_need_to_start_sway_with_dbusrunsession/jnxpxz7/?context=3#jnxpxz7 stating instead using d-bus, would use
seatd, I assume it has compatibility with d-bus. He recommends to uninstall d-bus in that case. I have no idea what seatd can do and if this is applicable to other distributions than Void Linux. So unfortunately I don’t know more than you. It makes sense that some sort of messaging is required in sandboxed environments.Funny enough I just looked in my Archlinux based system and look what we have, seatd is installed already. And
dbusis also installed.