• tuna@discuss.tchncs.de
      22·
      7 months ago

      XWayland normally runs x11 apps seamlessly (more or less) in Wayland

      XWayland rootful spawns a window which is like a virtual monitor running a full x11 session inside it. You spawn apps inside of the window using the DISPLAY variable

      • atzanteol@sh.itjust.worksEnglish
        26·
        7 months ago

        Still, the Xwayland window is missing a title bar that would allow for moving the window around.

        This is because Wayland does not decorate its surfaces, this is left to the Wayland client themselves to add window decorations (also known as client side decorations, or CSD for short).

        This however would add a lot of complexity to Xwayland (which is primarily an Xserver, not a full fledged Wayland application). Thankfully, there is libdecor which can fence Xwayland from that complexity and provide window decorations for us.

        This seems… ridiculous. Windows and MacOS developers don’t worry about creating decorations. And they don’t worry about that “adding a lot of complexity”. Even with X11 you get decorations from the WM without any work. I know I don’t understand the glory that is the Wayland architecture and that a bunch of folks will now angrily tell me all the numerous ways in which I’m not only wrong but but also stupid but… It just seems weird is all.

        • Confetti Camouflage@pawb.socialEnglish
          30·
          7 months ago

          iirc mandatory Client Side Decorations is only a Gnome on Wayland thing and everyone else has support for both Client and Server Side Decorations.

        • TurboWafflz@lemmy.world
          8·
          7 months ago

          Honestly I feel like it doesn’t really matter either way, it adds a little complexity for the people maintaining qt and gtk and things like that, but most actual application developers aren’t interacting directly with the display server so it doesn’t make much difference for them

        • Semperverus@lemmy.worldEnglish
          5·
          7 months ago

          I think that the reason for all the weirdness in wayland is because they are considering more usecases than just desktop with taskbar and window title bars with _ [ ] X buttons. Think signage, mobile interfaces, kiosks, and other weird non-traditional interfaces. Its why absolute window positioning is dumb the way it is too.

        • callyral [he/they]@pawb.socialEnglish
          4·
          7 months ago

          I though only GNOME cared about having client-side decorations? Probably why any GNOME app I have has an annoying toolbar when I’m using a tiling window manager.

          • leopold@lemmy.kde.social
            English
            3·
            6 months ago

            Indeed, but GNOME is big enough to veto against anything they dislike getting into Wayland. And indeed, TWMs were brought up as a big reason why CSD sucks; window decorations primarily contain controls for the window manager and the form these controls should take depends entirely on the nature of the window manager, therefore the window manager should draw the controls. But GNOME doesn’t want to perform the oh so difficult task of providing window controls to apps that don’t provide their own under Wayland, so too bad.

      • Cwilliams@beehaw.org
        1·
        6 months ago

        Its confusing that we also use ‘rootful’ to refer to a process running as the root user

  • penquin@lemm.ee
    9·
    7 months ago

    Can someone please eli5? Why do I never hear anything about the window manager in windows and macos? Why is all the fuss on our side on Linux? I’m genuinely asking.

    • Marmaduke@lemmy.world
      23·
      7 months ago

      A compositor is a program responsible for displaying program windows and things like the desktop on your PC. On Linux, the compositor is just a program that starts when the system starts. There are multiple desktop environments available, like Plasma or Gnome, each comes with their own compositor, you can choose which you want to use.

      Wayland is a protocol that the programs use to communicate with the compositor. Everyone decided to use Wayland, because if each compositor had their own protocol it would be silly, eg some programs would work only on Plasma or Gnome.

      It’s a replacement for a much older X11, which could no longer keep up with requirements of modern apps.

      You never hear anything about compositors on Windows or Mac because there’s only one available, you can’t choose.

        • LinusSexTips@lemmy.world
          1·
          7 months ago

          Oh man, brings me back to blackbox / xoblite on my old XP machine.

          I remember using notepad to change the config files, no auto formatting or error checking.

          Had no idea what I wanted out of it but I loved the minimal aesthetic.

      • penquin@lemm.ee
        2·
        7 months ago

        Thank you so much. Is there a reason why we have so many issues with scaling and font rendering and the other two OSs don’t (I’m not sure if they and they hide it, I don’t know). I tried gnome on my pc and the font got very blurry when I set the scaling to 175% for my 27" 4k monitor, switched to x and fraction scaling just disappeared. Why don’t the other two OSs have this issue?

        • azvasKvklenko@sh.itjust.worksEnglish
          1·
          7 months ago

          That’s a very long story, but in short - X11 was adopted as display system for Linux in 90’s at the very beginning because it was the only standard display protocol for UNIX systems at that time and it was natural consequence to take it along with the ability to port all the software that was made for it starting in 80s. The design of X started to quickly show its limitations and a replacement was considered. Wayland development was slow for a long time, because the priority was on usability of current graphics stack, which on X it was all in pretty bad shape even not so long ago. X is really not going anywhere with its feature while and only being in maintenance. Additionally, Wayland is very different and in some aspects, so it’s not possible to port things 1:1.

          Initially Wayland only supported integer scaling (if you used fractional scale in such scenario, it would render next integer and downscale to your resolution, causing some font rendering imperfections), but new protocol was introduced last year after years of debates and different attempts. New compositors paired with new clients will now render mostly perfectly in fractional scales, but clients that don’t support that will still use previous method. There are also X apps running on Xwayland. Some compositors (like kwin) allow those clients to render natively scaled, some upscale from 100%, so the windows are blurry.

          Other OS-es don’t have such problems, because:

          • they’re centrally controlled by just one entity with clear business strategy and unlimited budget
          • in monolithic systems where there’s just one UI and everything is tightly integrated, it’s much easier to innovate the software
          • closed source code don’t have to be perfect, they can hack it as much as they need as long as it’s doing well on end-users’ machine
    • giloronfoo@beehaw.org
      5·
      7 months ago

      It is being discussed because we’re in the middle of the transition from X to Wayland. Before there wasn’t much discussion. In a few years when it settles out there probably won’t be much discussion.

      Windows and Mac have never had a choice. There might have been significant changes to a window manager layer, but it would have been part of a larger version upgrade. Like between windows 3.1 and 95 or OS 9 to OS X. The visible changes would be closer to desktop environment like KDE and Gnome in Linux.

      • penquin@lemm.ee
        1·
        7 months ago

        Thank you so much. One more question, why do we have so many issues with scaling, font rendering and all stuff and windows and macos just do it? Why aren’t we doing similar?

    • edinbruh@feddit.it
      4·
      7 months ago

      In addition to what the others have said, windows has already had its big paradigm change (“similar” to the change from x11 to Wayland that is happening) in the past. It was around 2007 with windows Vista. They also didn’t get it quite right on the first try, but because Microsoft can do whatever they want, and in Linux you must convince the community that something is better, it was easier for them to just change everything under everyone’s nose.

  • AutoTL;DR@lemmings.worldBEnglish
    5·
    7 months ago

    This is the best summary I could come up with:

    Red Hat’s Olivier Fourdan just announced the stable release of XWayland 24.1 as the newest feature release for this X.Org Server code allowing X11 clients to work within the confines of Wayland compositors.

    XWayland 24.1 brings explicit sync support that’s long been in the works throughout the stack.

    The explicit sync support brings the most noticeable improvements for those using the NVIDIA proprietary Linux graphics driver with the R555 beta driver due out imminently with that driver-side support.

    Also of NVIDIA relevance in XWayland 24.1 is removing the EGLStream back-end now that NVIDIA has finally been supporting GBM across their recent driver versions.

    XWayland 24.1 also ships a number of rootful improvements including HiDPI and fractional scaling for the rootful mode, among other improvements.

    The brief XWayland 24.1 release announcement can be found on the Xorg mailing list.

    The original article contains 160 words, the summary contains 138 words. Saved 14%. I’m a bot and I’m open source!