• KubeRoot@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 days ago

    AFAIK all of Wayland is pushed onto the WM, because Wayland is just a set of protocols. It has some libraries, I think official ones, to help with implementing those protocols, but ultimately that’s a design choice that also means WMs don’t have to have those features, especially relevant for atypical WMs where the concept of windows might not exist, displays might not be two dimensional, input might be neither a mouse nor a keyboard.

    To my understanding, if somebody wants an unusual setup, on Wayland they might need to figure out implementation of protocols for their ideas. On X11, they might not be able to do anything because it enforces certain ideas of how a graphical environment works.

    That’s simply not a failure of Wayland, it’s a tradeoff they chose, and it seems dishonest when people say things “don’t work on Wayland” because the responsibility is deliberately moved to a portal or something.

    • TideElysium@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      3 days ago

      It is a trade-off they chose yeah, but for people on anything but KDE (really, though hyprland sway and gnome do most too) they’ve forced them to either catch up or die. I don’t know that that’s indicative of a great replacement project. For reference, I use Wayland & KDE fine, but if x11 had HDR I’d switch back to my i3 setup.

      • KubeRoot@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 days ago

        they’ve forced them to either catch up or die

        I think the “die” part is a bit of an overexaggeration, it’s true that they need to implement protocols if they want the features those protocols exist to provide, but the X way seems to have caused more problems in the long run. Niche projects will attract people who want that niche, hopefully despite missing features, and some people who can help implement those features.

        It’s worth noting that DEs can do things like use XDG portal implementations from another DE, I think it might’ve been Niri that does that.

        if x11 had HDR I’d switch back to my i3 setup.

        Then I can wish you that you get a worthy compositor/DE/whatever to replace i3 on Wayland. Either that or i3 somehow getting a Wayland implementation. I’m lucky in that I was comfortable on plasma with X, so switching to Wayland was mostly painless, though there were significantly more issues back then.

        • TideElysium@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          2 days ago

          It is an exaggeration in that Wayland isn’t outright killing x, but a lot of the talk surrounding both is that it’s supposed to. I’m not going to defend the state of X and the problems it’s caused because it’s a fugly old project, just when you look at something like pulse -> pipe wire, there wasn’t a big paradigm shift with it. It did the same job and better (to my knowledge!).

          I didn’t know that DEs could use others portal implementations, that seems neat?

          Yeah it’s the specifics of that that’s the issue for me though. I tried hyprland and many things are really cool about it but lots of things just break, and maintaining separate configs for what feels like core features was annoying. Then you get things like HDR performing differently between it and plasma, something that I’d hoped Wayland would just own. I’ll probably try niri and sway at some point, they both look cool

          • KubeRoot@discuss.tchncs.de
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 day ago

            It is an exaggeration in that Wayland isn’t outright killing x, but a lot of the talk surrounding both is that it’s supposed to.

            I interpreted that killing to refer to niche DEs rather than X, and while that isn’t happening yet, yeah, I imagine a future where software stops supporting X entirely.

            maintaining separate configs for what feels like core features was annoying

            That part specifically sounds like the fault of the specific DE? Wayland might be split into protocols, and some functionality might be handled by the portal, but ultimately it’s the compositor handling how it’s all implemented, and the configuration could well all be in one place.

            • TideElysium@lemmy.world
              link
              fedilink
              arrow-up
              2
              ·
              1 day ago

              Yeah, I guess I see the two as linked. I don’t think i3 is going to reimplement itself to stay available, nor would I expect them to

              Also yes I phrased myself very badly there: it’s a decision hyprland has made, where there are separate first party packages for core functionality that need their own configs. I’m sure it’s to allow for your own drop in replacements it just felt clunky to me. I don’t really have an issue with Wayland’s actual composition beyond I get lower input latency on X (which seems to put me in the minority), but they are both substantially lower and nicer to use than windows so I don’t care

              • KubeRoot@discuss.tchncs.de
                link
                fedilink
                English
                arrow-up
                1
                ·
                11 hours ago

                Regarding input latency, last I saw some testing suggests mixed results on performance, with X still being more consistent with slightly better performance overall, so it might still be winning in that regard. I haven’t tested it myself, but also didn’t notice problems when switching to Wayland, so maybe I was lucky again.

                • TideElysium@lemmy.world
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  36 minutes ago

                  Again, it’s within the realms of not mattering to me since both beat Windows, but it would be another thing I would welcome back. And for a lot of people, Wayland is more responsive

    • mittorn@masturbated.one
      link
      fedilink
      arrow-up
      0
      ·
      3 days ago

      @kuberoot @FishFace
      Yes, but this makes wayland good for everyrhing except normal desktop. It’s pretty good for VR/spatial desktops (where we do not want to deal with 2d coordinates), for some embedded setups where we only need to manage output to multiple displays or draw some overlays. But on normal desktop we need draw UI (wayland cannot do drawing at all!), position windows (limited), capture screen (actually done outside of wayland???) warp mouse (broken?), inject events for automation (yes, ei exist, but looks like very optional…), set screen resolution and layout (actually made different in every implementation?), manage clipboard (still depends on compositor?)
      So, wayland actually does almost nothing for desktop :(

      • KubeRoot@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 days ago

        Sure, Wayland “actually does nothing”, if you only and specifically mean things that are built into Wayland and only Wayland, the core project, itself.

        Meanwhile, as an actual user of a normal desktop on Wayland I can capture the screen, mouse warping works, I have an autoclicker, my screens have resolution, layout and scaling set, my clipboard and clipboard history work (with individual exceotions, accessible from a command line tool too). Hell, I even have HDR on because I found out it just works nowadays, even though my display is probably ass for HDR, but SDR content seems to look no different with it enabled.

        Window positioning is something that’s not finished, because the developers are trying to figure out a good way to do it and are taking a long time.

        Not sure what you mean by “drawing”, is it some pedantic bullshit again about how Wayland itself doesn’t dictate how you render stuff? Because I certainly have all kinds of GUIs running on my computer.

        So if you want a system that is hardcoded to only support things that are common nowadays and that will start breaking down in the next 10 years as things change and the code becomes impossible to maintain, maybe go contribute to XLibre. I will meanwhile patiently enjoy Wayland getting better, even if it might take years, because I have hope that this approach will work.