Hacker News new | ask | show | jobs
by thayne 825 days ago
I'm not opposed to having mechanism to opt in to client side decoration, but making it mandatory is problematic for several reasons:

1. Different apps will draw decorations differently, leading to a lot inconsistency. 2. It means apps designed for other environments that don't draw their own decorations won't have any decorations. 3. If your client doesn't use one of the big all encomposing gui toolkits (not every app needs that), then it has to implement the decorations itself, which is non-trivial to do correctly (I know because I have worked on it for such an app). 4. You can't reliably configure the appearance and behavior of the decorations in a central place for all applications.

Fuethermore, if clients always draw their own decorations, then if you use a tiling wm and don't want decorations at all, you are stuck with them.

2 comments

1) They will anyway, see below: https://news.ycombinator.com/item?id=39728575

2) Only if they use server-side decorations only. In Wayland, client-side is mandatory and server-side optional. So if they do not have decorations, they are broken.

3) You client should use one of the big frameworks. On other operating systems, they are mandatory anyway. Only Linux allows your client connecting to compositor directly. Use that power responsibly. Frameworks bring lot of stuff implemented for you. If you reject that, it is up to you to implement that yourself.

4) You can't even with server-side decorations either.

Yes, with tiling, you get them. However, many apps have toolbar there, so you need it anyway.

Even on a non-tiling WM, I'll rather have double decorations for GNOME apps than suffer the client side decorations.