I’ve been on Wayland for the past two years exclusively (Nvidia).

I thought it was okay for the most part but then I had to switch to an X session recently. The experience felt about the same. Out of curiosity, I played a couple of games and realized they worked much better. Steam doesn’t go nuts either.

Made me think maybe people aren’t actually adopting it that aggressively despite the constant coverage in the community. And that maybe I should just go back.

  • @onlinepersonaEnglish
    0•6 months ago

    I had it on a test system and Chrome/Chromium wasn’t happy. Slow af. Dunno if it had an impact on Firefox, but that used a lot of RAM and was very slow when sharing the screen.

    At least Waydroid worked flawlessly 👍

    For now, I’m back on X11 where I game. I’ll just wait for it come by default on major distros (“stable”), wait a little longer (stable for real) and then switch once nothing on my system needs “XWayland” or whatever. wine does AFAIK, so at least due to that, no Wayland for me.

    CC BY-NC-SA 4.0

    • @[email protected]
      1•6 months ago

      Chromium and Firefox work perfectly on Wayland. Minor issues like de-coupling tabs or something are made a bit differently, but thats cosmetic.

          • @onlinepersonaEnglish
            2•6 months ago

            Ah, the good old “works on my machine” 👍 Nothing but a good expression of disregard of other people’s problems.

            Principal Skinner: Is there a problem with Wayland and Chrome/Chromium/Firefox for some people? Nah, their system is broken

            CC BY-NC-SA 4.0

            • @[email protected]
              1•6 months ago

              If you give me more details maybe I can say something else :D

              At least on Fedora, official tarball (firefox and firefox-bin), Fedora Firefox, Librewolf RPM, Librewolf Flatpak, Firefox Flatpak, torbrowser flatpak, Thunderbird flatpak, selfbuilt Firefox nightly, Chromium RPM, Chromium Flatpak and Brave RPM all work flawlessly when it comes to Wayland.