4 ms·
> And then so many things seem to follow the "unix functionality" and as a result they're half baked tools that aren't really working properly IMHO. I'm going
by yjftsjthsd-h 4y ago
> And then so many things seem to follow the "unix functionality" and as a result they're half baked tools that aren't really working properly IMHO.
I'm going to disagree pretty strongly with that. In fact, I think most of its problems are that it threw the Unix philosophy out the window. While it's true that it suffers from having made everything a implementation detail that can theoretically be plugged in with a different component, the problem is that they forced everything important to go through the compositor, which bottlenecks composiblilty and doesn't allow you to actually replace individual components without support from the (usually incomplete) monolith in the middle.
- falseassertions 4y agoExcept that nearly everything that makes the usual years-out-of-date Wayland gripe lists here are ALL specified protocols now, it's just a matter of time until they're implemented widely enough to put this to rest. Fractional scaling, hotkeys, gamma control, screen capture, etc, all have protocols.
- yjftsjthsd-h 4y agoI don't believe that this will happen in practice in any event. First, implementations have... let's say personality conflicts? That is, I would be shocked if GNOME replaces its screenshot protocol with the "standard" any time soon. Second, even when it's true it requires every single compositor to actually connect all the bits up. For instance, I don't use QWERTY if I can help it. So a little while back, I tried a new compositor that was based on wlroots, which supports changing keyboard layouts. Guess what I couldn't do, because that specific compositor hadn't gotten to plumbing that specific feature through? Guess what works on every single X11 window manager, no matter how barebones, because X11 can manage separation of concerns?
- adgjlsfhk1 4y agohdr is still mia
- kaba0 4y agoAs opposed to the single, so-huge-that-nvidia-ships-binary-blobs-for-it xserver implementation?
- yjftsjthsd-h 4y agoYes, actually; the X server was awful, but it was a single contained point of awfulness that allowed everything else to be trivially interoperable. Breaking that apart could have been good except that the way they actually did it mixed far too many concerns into the graphical server (compositor), so while we have more of them, in practice you can't actually mix and match the rest of the system anymore.
- kaba0 4y agoIt is a display protocol, responsible for displaying things. A compositor is a must for that, it is not additional complexity at all. What you would want to mix is a window manager, and there is no reason why that can’t be done with this model (and is pretty much what wlroots does). But I do agree that a cathedral model can have benefits.
- kelnos 4y agoNot sure what you mean; wlroots still assumes that the window manager and compositor is in the same process. Wayland itself assumes that those things are also in the same process as the display protocol/server. With X11, if someone wanted to write a window manager, they could do that and only that, without having to write a compositor or display server. Wlroots certainly simplifies those latter two bits, but there's still a lot of work to do to use it. Beyond that, Wayland's mess of extension protocols are generally incomplete. I've been working on "porting" parts of Xfce to Wayland, and there are a significant number of things that just cannot be done at all right now without integrating it directly into the compositor process. The extension protocols necessary to do even a fraction of this table-stakes stuff are often experimental or non-standard, and even when they do exist, are often missing critical pieces. As an example: say you want to write a dock-type app that only shows the list of toplevel windows present on the current workspace (and when you switch workspaces, it'll show the windows on the new workspace). Nope, you can't do it. The workspace protocol itself has been languishing in Freedesktop GitLab[0] for two and a half years, and even if that was standardized, it doesn't interact with the Foreign Toplevel protocol at all, so you have no idea what windows are on which workspaces. So currently the only solution is: your dock app has to live in the same process as the compositor, where it has access to all the compositor-specific data around workspaces and windows. (Sure, you could build a d-bus interface, or something like that, but that would be specific to your one compositor... and a d-bus interface is the moral equivalent of a Wayland protocol, which is what you should be using anyway.) [0] https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/40 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m...