7 ms·
> Both win32 and macos draw decorations client-side. That's technically true but misleading. Yes, they have client-side decorations, but also a single and unif
by sph 4y ago
> Both win32 and macos draw decorations client-side.
That's technically true but misleading. Yes, they have client-side decorations, but also a single and unified UI toolkit all applications use. So effectively _you_, the application writer, do not have to care about decorations.
Whereas, on Linux Wayland, if you want to support GNOME, _you_ have to care about decorations, or you have no titlebar nor X button. Which means you need to link against libdecor yourself to get that functionality and in theory wouldn't be that bad if that library was maintained and functional, but it isn't. The one stable tag is 0.1.0 from one year ago, and it still causes massive lag when trying to resize a window if you have more than 1x scaling: https://gitlab.gnome.org/jadahl/libdecor/-/issues/37 https://gitlab.gnome.org/jadahl/libdecor/-/issues/37 — Don't be mislead by the title, affects AMD as well.
libdecor is the _only_ way to have decorations on Wayland on all major DEs, unless you actually want to write the entire decoration code yourself. And it's buggy and unmaintained. And, cherry on top, libdecor does not match the desktop environment's look and feel, so your app has decorations that look completely out of place.
I'm a GNOME and Wayland apologist, but libdecor is terrible, unavoidable, and exists only because GNOME couldn't pull their head out of their arse and created this situation.
Not supporting server-side decorations is only a good idea in a vacuum, not in the real world. Applications should be able to choose whether they care about it (i.e. Firefox for their UI), or not at all (i.e. a video game window), as it's possible to do in Windows or macOS.
- PlutoIsAPlanet 4y ago> Whereas, on Linux Wayland, if you want to support GNOME If you want to support GNOME, you use GTK or use a library that interfaces with GTK. The binary compatibility with other desktops is just a "nice thing" to have, but GNOME really doesn't care for apps not made for GNOME. There was a project where Qt would interface with GTK and let GTK handle its window management (similar to macOS/Windows), rather than dealing directly to the display server, but I think its dead.
- chrismorgan 4y ago> but GNOME really doesn't care for apps not made for GNOME And this is the sabotage of GTK and the Linux desktop that I’m speaking of.
- hutzlibu 4y agoBut there is a great difference between not caring and sabotage. Not caring is passive neglect, maybe not nice, yes. But sabotage is activly disturbing something with evil intentions. So this is a strong accusation, for which I like to see some more solid evidence, to believe it.
- chrismorgan 4y agoIt’s the co-opting of GTK that drives that. GTK used to be fairly platform-neutral under Linux, and at least moderately neutral on other operating systems, adopting some of their conventions and with theme matching being possible. It has become increasingly aggressively GNOME-bound, so that with every major release it becomes more and more difficult to produce anything that looks or feels native on any platform other than GNOME. (Even under Linux; and it’s completely impossible to produce a good result for Windows any more.) Gutting theming. All but forcing a particular idiosyncratic form of overlay scrollbars. Insisting on client-side decorations and refusing almost to acknowledge the very existence of server-side decorations (in both GNOME Shell and GTK, from both ends). The list goes on, though these are probably the three biggest ones. From time to time they take a small step back (e.g. libadwaita) or present an apparent alternative (e.g. libdecor), but those options never work well, and I strongly suspect that, whether consciously or unconsciously, they’re just to try to placate the mobs. (libadwaita hasn’t gone anywhere near far enough, to the point where they might as well not have bothered: GTK is still riddled with mandatory GNOME HIG stuff that is strongly opposed to conventions on other platforms.) ’Tis said: never attribute to malice what can be adequately explained by incompetence. But malice learns to wear incompetence as a mask, and organisations weaponsise incompetence. I doubt that individual GNOME developers mean any malice. There may be no malice intended from any of the GNOME project leaders. But over the last few years I have steadily become convinced that cumulatively their actions and policies are active sabotage towards every last bit of the Linux desktop that isn’t GNOME.
- samus 4y agoThis is a valid take, but it further fragments the Linux desktop. There are already too many different standards and technologies and transitions going on. Some of them for good reasons admittedly. Desktops only being compatible with their closely aligned toolkit is the last thing we need.
- kaba0 4y ago> also a single and unified UI toolkit > Whereas, on Linux Wayland, if you want to support GNOME, _you_ have to care about decorations, or you have no titlebar nor X button And you have basically two UI toolkits for linux that also does everything for you without caring about it, how is that different? Also, if you do decide against using said frameworks, you also have to care about accessibility and a million other things that you weren’t going to do either way let’s be honest, so I don’t know, it seems to be a non-issue to me. Use libraries instead of reimplementing everything from scratch.
- badsectoracula 4y ago> And you have basically two UI toolkits for linux That isn't the case. There are several UI toolkits on Linux, they may not be as widespread as Qt and Gtk are, but they are used by many applications. And even with Qt/Gtk, their developers (especially Gtk) regard each major version as a separate library.
- kaba0 4y agoSure, but then it is the job of those framework developers to.. abstract away the underlying display manager, so they should port their framework to support wayland as well, and application devs can just continue to write against this abstraction. I still see no problem here.
- bluGill 4y agoThose others - for better and worse have less developers. Having to figure out two different types of decorations is a mess that they don't have time to, so I can't blame them for picking one.
- kaba0 4y agoThat is inherent in open-source/bazaar-style development, and we can all help wherever we can. There is no entity like Apple/Microsoft mandating that we change to Y from X.
- ben-schaaf 4y ago> Yes, they have client-side decorations, but also a single and unified UI toolkit all applications use. MacOS has Carbon and Cocoa (and WebKit). QuartzCore lets you make windows, but doesn't give you decorations. Pretty similar to libwayland. Windows has Win32 and while it does provide window decorations new UWP apps and thus the rather long list of various UI toolkits made by microsoft provide their own decorations. This is why dark mode doesn't work on some apps. So the situation is again pretty similar to libwayland. Window decorations aren't even the same for different versions of Windows/macOS, so if you want to implement your own you'll end up providing multiple implementations for each platform. The real difference is that there's a single entity with the will to go through each and every UI toolkit and update them all to look the same ahead of a new major version. That's not to say that server-side decorations are therefore bad; it's just that Microsoft and Apple put the resources behind client-side decorations to make them work as well as they do.
- PaulDavisThe1st 4y ago> MacOS has Carbon and Cocoa (and WebKit). QuartzCore lets you make windows, but doesn't give you decorations. Pretty similar to libwayland. Carbon was deprecated well over a decade ago, and has not been available for several iterations of macOS. > The real difference is that there's a single entity with the will to go through each and every UI toolkit No, the real difference is that it is absolutely clear on macOS and Windows what the obvious/preferred/blessed UI toolkit is, and anyone who chooses to use something else is extremely aware of the consequences of that (and if they weren't before making that choice, they will be very soon afterwards). On Linux, the situation is more or less the opposite. Not only do you have the choice of actual UI toolkit libraries, with none being more or less "blessed" than any other, but with Wayland's adoption, the fundamental windowing technology that sits on top of the video drivers is also not a single thing either.
- kevin_thibedeau 4y agoWhat is the blessed UI on Windows? They have more than one.
- ben-schaaf 4y ago
- totetsu 4y agoJust started using wayland gnome yesterday. Is this why Firefox has a completely different mouse pointer to the one I set in gnome?
- chrismorgan 4y agoAh, cursors. This seems to be one area where the Wayland situation is comically bad. I use Sway, and have these in my config: output eDP-1 scale 1.5 seat seat0 xcursor_theme Adwaita 96 Well, I get at least six different cursor sizes depending on the window hovered. Sample apps with rough eyeballed scales: Firefox gets 1×, XWayland gets 1.5×, Alacritty 2×, Sway 2.5×, Zeal 4×, and I can’t remember what the app was that had something else again…
- tedcrilly 4y agoIs it on modern Ubuntu? Because it may be caused by the fact that Firefox is packaged as a snap.
- totetsu 4y agoYes on 22.04 jammy.
- sph 4y agoProbably some ubuntu fuckery. I have Firefox in a container as well (but it's Flatpak) on Fedora, and it uses the same cursor as the rest of the system.
- fuckstick 4y ago> Yes, they have client-side decorations, but also a single and unified UI toolkit all applications use. Other than MacOS, kinda sorta, this just isn’t true and hasn’t been so for years.
- miohtama 4y agoThis post is a nice case study why the year of desktop Linux is unlikely to happen any time soon, or didn’t happen in the past. It takes large engineering work to write all the software, and needs discipline and people working on very boring areas and aspects of the UI. I find it unlikely any OSS community will ever pull it off, unless there is a clear monetary incentive to fund it and work hard.
- sph 4y agoThere is no reason to think it can't be pulled off, but the Linux world suffers from catastrophic amounts of bike shedding. The Linux desktop needs a leader figure. A Steve Jobs, or a Linus Torvalds. Leave it to the community, and everybody wants to reinvent the wheel and paint it their favourite colour. Directed innovation can only be achieved from a single vantage point, not by a committee, let alone a ragtag of independent actors.
- encryptluks2 4y agoHow do you propose that people work for free at the behest of a leader directing such unpaid contributors how to o their work? Slave labor?
- sph 4y agoHow did Linus convince hordes of people of contributing to his kernel, his trademark, for free? The official repo is under his personal account at github.com/torvalds/linux And regular for profit companies aren't incompatible with Linux. Canonical, Red Hat, etc. make billions from open source. Let me stress this again: the only reason the Linux desktop sucks is organizational. Not monetary, not technological. Linux would be a niche project today if Linus had been replaced by a committee or other loose organization. The Linux kernel is successful because there is a person at the top saying "No." The Linux desktop has no such thing. None of the singular desktop environment have such a thing. GNOME has no BDFL, nor does KDE. So its endless bikeshedding and churning and going nowhere.
- 4y ago
- yxhuvud 4y ago> if you have more than 1x scaling: https://gitlab.gnome.org/jadahl/libdecor https://gitlab.gnome.org/jadahl/libdecor It affects anything which put any sort of strain on the compositor. A hi poll-rate mouse also trigger the issue simply because there will be more resize events. Why gnome-shell doesn't apply some sort of back-pressure or opportunistic skipping of events when it is behind is beyond my understanding.
- curt15 4y ago>Whereas, on Linux Wayland, if you want to support GNOME, _you_ have to care about decorations, or you have no titlebar nor X button. Does GTK not manage the decorations for you?