@TheEvilSkeleton I'm still irked by how #GTK does title bars client-side though. Many environments use server-side title bars which can work differently, and GTK apps tend to look pretty chubby in i3 etc. :-/ Maybe GNOME and KDE don't compete how they used to, but as a power user this always seemed so wrong to me.
(I'm currently a #GNOME user btw. I might go back to sway though someday.)
@gloopsies @TheEvilSkeleton Yeah, CSD does enable a lot of UI potential; putting widgets in the titlebar works great, and I think it so elegant when modern GTK apps change the titlebar depending on context. (1/)
From a more philosophical point of view, window decoration is more of a system element – you mainly move, close, resize, maximize, minimize, and many other special things your system does, from it, so shouldn't it be part of the system rather than the applications? The #unixphilosophy comes to mind. (3/)
@golemwire I agree that it's lame, but there's not much they can do about it. CSDs give the opportunity to have multiple elements in the bar. It's why GNOME apps have several buttons at the top bar, like the hamburger menu.
Meanwhile, GIMP has a titlebar+menubar setup, which in my opinion looks awful and takes a lot of space. Steam for example uses CSDs, to merge the menubar and titlebar, which is a much better approach.
Needless to say, you can remove the bar using CSS.
@golemwire @TheEvilSkeleton
I understand where you're coming from, but that's the only way to make title bar actually usable and escape all the menu bars all the KDE apps have. If used as expected, Gnome apps with title bars have more functionality and are more space efficient then KDE alternatives