4 ms·
I've been an Xfce user since 2004 (and was a core developer until 2009), and continue to use it to this day. My biggest worry is that, since the GNOME folks co
by kelnos 6y ago
I've been an Xfce user since 2004 (and was a core developer until 2009), and continue to use it to this day. My biggest worry is that, since the GNOME folks control GTK+, it will morph into something that non-GNOME projects (like Xfce) can't realistically use.
Granted, Xfce has gone through a toolkit change before, but switching again would be too much of a burden.
I feel like there was a sweet spot in the mid and late 00s when there were efforts to promote cross-desktop standards (the "XDG" in those environment variables means "cross-desktop group") that made it easier to write apps that would integrate well with any environment, regardless of what toolkit you were using. But at some point in the early 10s that degenerated into GNOME ramming "standards" down people's throats and going their own way without any attempt to work with the rest of the community.
It's an interesting coincidence that systemd's rise (with similar standards-forcing and advocacy for tight coupling) was somewhat concurrent with GNOME's descent into community hostility.
- ohazi 6y ago> My biggest worry is that, since the GNOME folks control GTK+, it will morph into something that non-GNOME projects (like Xfce) can't realistically use. This is a valid concern: https://askubuntu.com/questions/477178/avoid-double-titlebar-in-gnome-apps-running-under-xfce https://askubuntu.com/questions/477178/avoid-double-titlebar... They've since added support for client-side decorations, but it arguably wasn't by choice. It definitely feels like a cat and mouse game now.
- int_19h 6y agoSpeaking of window decorations, the arguments from GNOME developers on this issue are nuts. Do they really not understand why games etc need this, or that literally every other desktop environment (including Windows and macOS) provides an equivalent facility? https://gitlab.gnome.org/GNOME/mutter/-/issues/217 https://gitlab.gnome.org/GNOME/mutter/-/issues/217
- jhasse 6y agoBoth Windows and macOS only provide one API to create a window and could switch to CSD-only tomorrow without anyone noticing. In a way they already have since they work differently anyway (no server/client architecture). So they are a bad example as they went the toolkit-way, which GNOME also wants.
- int_19h 6y agoI'm not even sure about Mac, but in Windows, there's no distinction, because there's no "client" and "server". But from developers' perspective, it's less about CSD vs SSD, and more about being able to say, "I just want standard window decorations, please and thank you", vs not being able to. Gnome devs' suggestion to just use Gtk3 for this is not really equivalent, because on both Windows and macOS, the library that offers the window creation API is core part of the OS - it's technically a dependency, yes, but it's the one that nobody actually cares about. On Linux, Gtk3 is a dependency that people do care about, because it's not guaranteed to be present, and requiring it often means doubling the sheer number of packages that an app like that might need. Gnome doesn't care, because they see themselves as a platform akin to Windows and Mac - so if you intend your app to run on Gnome, then you compile it for Gnome (and then assume that Gtk3 is always there). But, of course, this attitude amounts to saying that they don't really care about compatibility with apps for "just Linux". Which is exactly why they're getting so much pushback on this.