GNOME devs simply can’t “tolerate” SSD, and force CSD in every scenario for GTK4. My machines running Wayland only have CSD for fully custom apps (like Steam) and every GTK4 app.
What problem does CSD solve? I’d think “some apps look and work differently” is a pretty bad tradeoff for “I want to cram custom stuff in the title bar which was more or less universally treated as owned-by-the-system for the first 35 years of GUIs at least?”
GTK/GNOME seem to be making themselves actively hostile towards customization, which seems a great way to lose enthusiasts.
Oh yes, Gnome’s famous stance on server-/client-side decorations
Well, Wayland forces client side decorations which I’ve never agreed with.
GNOME devs simply can’t “tolerate” SSD, and force CSD in every scenario for GTK4. My machines running Wayland only have CSD for fully custom apps (like Steam) and every GTK4 app.
No, that’s Gnome, not Wayland. KDE still prefers SSD on Wayland.
Wayland does force clients to be able to cope with a compositor that doesn’t do SSD - CSD support is mandatory, SSD optional.
What problem does CSD solve? I’d think “some apps look and work differently” is a pretty bad tradeoff for “I want to cram custom stuff in the title bar which was more or less universally treated as owned-by-the-system for the first 35 years of GUIs at least?”
GTK/GNOME seem to be making themselves actively hostile towards customization, which seems a great way to lose enthusiasts.
Exactly. Their stance is CSD or nothing.
More power to the developers to customize their design is always a great recipe to get a inconsistent mess.