• While it actually works, there are truly some missing features obviously. The hope is, when lot of major distributions and desktop environments stop supporting X11, then application developers and Wayland developers have to find a solution quicker. This will accelerate development of Wayland, at least the remaining issues.

      One area where Wayland needs to improve is support for various accessibility features.

      • notabot ( notabot@piefed.social ) 
        link
        fedilink
        English
        arrow-up
        25
        ·
        1 year ago

        That does feel rther like jumping out of a plane and hoping you can finish making your paracute before it’s too late.

        The concept of moving on from X11 is a good one, but making Wayland just a protocol that every compositor has to implement separately, and having so many optional larts to the spec seems like a guarantee that the ecosystem around it will never properly mature.

        The KiCad developers have a good article about some of the issues with Wayland here.

      • HakFoo ( HakFoo@lemmy.sdf.org ) 
        link
        fedilink
        arrow-up
        10
        ·
        1 year ago

        This is big “if we break your old toys, you’ll HAVE to play with the new ones” energy.

        Tell me when they port FVWM. Seriously. FvwmButtons-- a pretty trivial dock except it can swallow other windows-- seems like it would be out-of-bounds on Wayland unless it was owned by the compositor itself to access the other windows. I don’t see any of the new taskbar-tools used with Wayland compositors offering similar functionality (I could be wrong) and that seems an amazing loss of feature parity.

  • esa ( syklemil@discuss.tchncs.de ) 
    link
    fedilink
    arrow-up
    24
    ·
    1 year ago

    Between that and the uutils-coreutils, Ubuntu 25.10 sounds like it’ll be an interesting experience for users, especially those with accessibility and internationalisation needs.

    • I fully agree with you on the accessibility front. It’s not even good on X11, but it’s unusable on Wayland, from what I understand :( Accessibility on Linux needs a massive funding and development initiative, and it needed to be done a long time ago.

      But uutils is pretty solid. I’ve swapped out my GNU coreutils entirely (on Arch, not Ubuntu, because I value my time too much to be troubleshooting broken snaps) and haven’t run into any issues. I think people are underestimating how close the compatibility already is. I’m sure something I use at some point will try to invoke an option that doesn’t exist in the uutils version, but it’s been solid for me so far.

      • Yeah, I think those are just lacking in the internationalisation?

        People like me, who at most have some reading glasses needs and have their computer set to generally English utf-8 will be likely be fine.

        • internationalization

          Interesting point. I don’t actually know about that. What can the GNU coreutils do with regard to internationalization? Just the output of commands, or can they also internationalize stuff like command args?

          • I’m generally an en_*.UTF-8 user (even tried en_DK.UTF-8 for a bit for a reason we’ll come back to), so I don’t have a complete picture of it and would have to go look at the documentation or source for that, but I’d expect

            • documentation
            • date formats: en_DK.UTF-8 should give you ISO8601-formatted dates, if I can’t have that I at least want DD/MM/YYYY; the US-american nonsense is just plain unacceptable
            • sorting: e.g. Norwegian will have …zæøå and expect aa to be sorted as å, the Swedes have …zåöä, the Germans …zäöü, the Turks will want ı and İ sorted and upper/lowercased correctly, and there are some options around how you deal with “foreign” letters and diacritics.
            • Probably more stuff relating to LC_* that I can’t think of off the top of my head

            but in any case, an ls -l output should be different depending on your locale, and in ways you likely don’t even think about as long as it looks normal.

      • Yeah, I think the fact that the next LTS will be 26.04 is the driver here, I just get the impression that things might get a little rocky and that they might’ve been better off had the next LTS been further into the future.

        But it’ll be a real smoke test release, at least. Hopefully they have enough resources to fix the issues that are uncovered, and don’t wind up reverting for the LTS, or with a crummy LTS.

  • Gnugit ( Gnugit@aussie.zone ) 
    link
    fedilink
    arrow-up
    17
    ·
    edit-2
    1 year ago

    How is wayland nvidia gaming at the moment?

    Several months ago I tried gaming on wayland with nvidia and it was completely broken for me.

    EDIT: Two days on wayland nvidia now, both gaming and using NVENC in OBS. It’s been amazing.

    • disco ( disco@lemdro.id ) 
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      Just make sure the kernel modules are enabled and so are the systemd services. Shouldn’t have a problem. It’s been butter since they released the VRR fix a few months ago

          • Gnugit ( Gnugit@aussie.zone ) 
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            I switched to wayland since arch had manual intervention on the latest update for kwin-x11 I decided it was time to take the plunge.

            So far it’s actually amazing. In two days of gaming I’ve had a great experience and OBS has been awesome. I particularly like the pipewire handling of OBS over the x11 window capture.

            I also went through the wayland and nvidia arch wiki pages before I started up my game and it looks like everything is now implemented by the nvidia drivers. I’m happy nvidia might finally be catching up, though, I won’t hold my breath as it still looks a little like the absolute bare minimum.

    • murvel ( murvel@feddit.nu ) 
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 year ago

      Depends on the desktop environment in my experience. On Fedora Gnome it was an unstable mess with my Nvidia RTX card but Fedora KDE Plasma has been stable.