Skip Navigation

Do you daily drive Wayland, if so since when, if not when will you?

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.

294

You're viewing part of a thread.

Show Context
294 comments
  • I didn't even point out accessibility? That was a different user. You can't even read bro talk about imagining and then spitting garbled nonsense. Go back and read everything and then I might reply seriously.

    I've not seen Wayland ever outside of this subreddit 🤣

    I'm sure distro of the month somewhere prolly implemented it but us Debian chads stay winning.

    I swear this is a psyop to kill of desktop Linux. Come back when screenshotting works correctly 👌

    • Debian has implemented it. Screenshotting has worked perfectly for years, maybe half a decade at this point.

      edit: I just checked, screenshotting has been working since 2015 https://github.com/swaywm/sway/issues/1

      Debian has been using wayland by default on gnome since 2019.

      This is an impressive level of confidence for someone who has no idea what they're talking about.

      Also, seeing as you're the guy who doesn't even have accessibility problems, that means you have... no problems.

      Remind me again, what is so bad about wayland?

      • since 2015

        Why did it ever not work?

        Oh it's because the protocol forbids apps accessing the output of other apps without special support for it, so unless apps manually include support for Wayland, it will not work.

        With many apps that don't even do anything related to screenshotting or overlays - like Guake - it still does not work.

        So most of my usual workflow is just broken by Wayland, productivity utterly shattered by some middleware crap and for what? Why?

        Why? Why must the graphical protocol of all things break random software incl. accessibility, overlays etc.? No other OS has ever had this issue. No other OS finds it a security concern to allow apps to see other apps.

        The only reason Wayland does is because it's just terribly designed from its very conception despite the constant warnings from other Devs and users.

        Oh and then there's the Nvidia driver support...

        Look at what they did with PulseAudio - now that's the right way to do it, users don't even know the difference except suddenly everything just works a bit better.

        default

        Ye I know that, this isn't the own you think it is as the GNOME Devs lost their mind long ago in many other ways as well.

        • Oh it’s because the protocol forbids apps accessing the output of other apps without special support for it, so unless apps manually include support for Wayland, it will not work.

          It's no more special than what they had to do to support X...

          With many apps that don’t even do anything related to screenshotting or overlays - like Guake - it still does not work.

          Actually guake already works perfectly.

          So most of my usual workflow is just broken by Wayland, productivity utterly shattered by some middleware crap and for what? Why?

          Security, proper rendering, mixed refresh rate displays, color management, HDR, no more insane hacks, I could go on. Also, you can't actually name a way in which your productivity is actually affected.

          Why? Why must the graphical protocol of all things break random software incl. accessibility, overlays etc.? No other OS has ever had this issue. No other OS finds it a security concern to allow apps to see other apps.

          Other OS's DO have this issue, you have no idea the things macos has enforced, and we have backwards compatibility using xwayland, being forced to update to a new standard IS normal for operating systems, linux just delayed it for as long as possible. The problems with X11 are MUCH more vast than the problems other operating systems have.

          The only reason Wayland does is because it’s just terribly designed from its very conception despite the constant warnings from other Devs and users.

          Name one actual problem with the design.

          Oh and then there’s the Nvidia driver support…

          That's 100% nvidia's fault and almost completely resolved

          Look at what they did with PulseAudio - now that’s the right way to do it, users don’t even know the difference except suddenly everything just works a bit better.

          That wouldn't have worked with X11 at all, because x11 is so fundamentally broken that making a successor to X is completely actually impossible, there's a reason all the X11 devs which you believe are so brilliant for making x11 decided to switch to developing wayland, and decided that what you want is actually completely impossible while making an actually well designed desktop. Please actually look into the history of this. The people who actually know how X11 works, refuse to work on it, and for very good reason. If what you were saying was true, there would be an X12 project in the works... but there is not, because it is fundamentally awful.

          Ye I know that, this isn’t the own you think it is as the GNOME Devs lost their mind long ago in many other ways as well.

          It's also the default on KDE now, also, I don't understand why you seem to believe they should've rushed this out, what they did was correct, x11 wasn't going anywhere, you can still use X11, the point of wayland was to redesign things from the ground up to be as perfect as possible, and they're (slowly) achieving exactly that.

          Use x11 if any of your usecases aren't met by wayland, it's not like they deleted it. But wayland is the future. They were right to make it partially non-backwards compatible, they needed to restart from scratch.

You've viewed 294 comments.