After more than forty years, everyone knows that it’s time to retire the X Window System – X11 for short – on account of it being old and decrepit. Or at least that’s what t…
My big complaint with Wayland is that the ecosystem has not really developed an effective standardization process.
With web browsers, you would get browsers doing their own thing; then copying each other’s thing, then writing down a standard for that thing, then all switch to the standard.
With Wayland, you get: https://wayland.app/protocols/
For as old as Wayland is, there are 5 standard protocol extensions (plus some updates to the core protocol). A bunch sitting in the standardization pipeline. Then a whole bunch of redundant protocols because each compositor is just doing their own thing without even attempting to standardize.
It doesn’t help that one of the major compositor (Gnome/Mutter) has essentially abandoned Wayland for everything beyond the core capabilities in favor of offering additional functionality over a separate DBus interface.
Let me be clear, I am not here to defend the Wayland standards process. The GNOME guys in particular are a nightmare and heavily resist everything they do not themselves need. If what you want to complain about are some of the people “in Wayland”, I am on your side.
That said, xdg-desktop-portal and DBUS are part of the Wayland world as they are part of then freedesktop.org standard. Red Hat has a vision for the Linux platform. This is it.
But this is like saying the web is not just HTML anymore because it also requires JavaScript. Everybody is on board with dbus. It is how you do IPC to sandboxed Flatpak apps too…
My big complaint with Wayland is that the ecosystem has not really developed an effective standardization process.
With web browsers, you would get browsers doing their own thing; then copying each other’s thing, then writing down a standard for that thing, then all switch to the standard.
With Wayland, you get: https://wayland.app/protocols/ For as old as Wayland is, there are 5 standard protocol extensions (plus some updates to the core protocol). A bunch sitting in the standardization pipeline. Then a whole bunch of redundant protocols because each compositor is just doing their own thing without even attempting to standardize.
It doesn’t help that one of the major compositor (Gnome/Mutter) has essentially abandoned Wayland for everything beyond the core capabilities in favor of offering additional functionality over a separate DBus interface.
Let me be clear, I am not here to defend the Wayland standards process. The GNOME guys in particular are a nightmare and heavily resist everything they do not themselves need. If what you want to complain about are some of the people “in Wayland”, I am on your side.
That said, xdg-desktop-portal and DBUS are part of the Wayland world as they are part of then freedesktop.org standard. Red Hat has a vision for the Linux platform. This is it.
But this is like saying the web is not just HTML anymore because it also requires JavaScript. Everybody is on board with dbus. It is how you do IPC to sandboxed Flatpak apps too…