On the Gnome project and “my way or the highway”
I would be happy if they stop opposing server side decorations in Wayland. Weston and Mutter are probably going to wind up being basically the only two Wayland WMs that don&#x27;t support it, making GNOME an unfortunate and avoidable edge case.<p>I think the CSD initiative is fine if it&#x27;s a choice. However, I can&#x27;t choose to not use GNOME on behalf of my users. Libdecor is a bad and C-centric solution to the problem. I know Mutter is designed in such a way that makes this hard; that was a pretty big misstep in my opinion.<p>Likewise for other things that GNOME Project pushes.<p>Here is a great example. Wayland has a protocol for inhibiting idle called inhibit-idle. GTK won&#x27;t use it. Instead, they want you to use a DBus interface from the enormous XDG Desktop Portals API. They refuse to have any kind of discussion about it. End of story.<p><a href="https:&#x2F;&#x2F;gitlab.gnome.org&#x2F;GNOME&#x2F;gtk&#x2F;-&#x2F;issues&#x2F;2202" rel="nofollow">https:&#x2F;&#x2F;gitlab.gnome.org&#x2F;GNOME&#x2F;gtk&#x2F;-&#x2F;issues&#x2F;2202</a><p>This pattern repeats for even silly things. Like the size of the mouse cursor on HiDPI screens? No problem bro, just use this bespoke DBus API.<p>This is all assuming you want to use DBus. Why? Wayland is already the thing that you speak to talk to the display server. Why use another protocol for basic functions like this? If DBus is so great, why do we even need the Wayland protocols in the first place? (Dbus is not great.)