Does Wayland really break everything?
pointieststick.com
I’ve written some other posts on Wayland recently, and it’s time for another one! Feel free to skip it it you aren’t interested in a discussion of Wayland and platforms. Many may …
    •  vrighter   ( @vrighter@discuss.tchncs.de ) 
      7•6 months ago

      “that thing you used to do is now impossible to do consistently across different implementations, if at all. But it’s all ok, because we have decided it’s not our responsibility!”

      That is not what users want to hear. From a user’s point of view, it is broken.

      •  MiddledAgedGuy   ( @MiddledAgedGuy@beehaw.org ) 
        2•6 months ago

        I see what you’re getting at. It’s a matter of perspective, I guess.

        If you presented someone with a list of features from two similar but different pieces of software, they wouldn’t say software b is broken because it’s featureset is different from software a, right? But I acknowledge it’s not that straightforward. It’s more like telling them software b is going to replace software a that you’re currently using, get ready to say goodbye to some features.

        I still don’t consider wayland broken, but I understand argument that it is.

        •  vrighter   ( @vrighter@discuss.tchncs.de ) 
          2•6 months ago

          yes, if i combare kicad with blender, neither is broken because they have different features. But also, nobody is telling users that kicad’s days are over and it should be replaced by blender. If they did, and a user wanted to design a circuit board, the user is out of luck. The user is told that it is a replacement. From the user’s point of view it most definitely is not.

          The probeem isn’t just that wayland doesn’t do everything x does. But that users are told that it will replace x, deal with it and quit complaining.

          We have to keep in mind that the fact that we know what wayland is in the first place puts us squarely into the “technical user” category, not regular users. Regular users are the ones who don’t even know (nor should they have to care) what wayland even is

  •  slembcke   ( @slembcke@lemmy.ml ) 
    15•6 months ago

    I’ve been using Wayland daily for a few years (2020 at least?) on intel and AMD graphics and have had few complaints:

    1. Some games didn’t work right a few years ago. (Under Proton or otherwise. Haven’t had issues for a while)
    2. RenderDoc, a vital bit of graphics debugging software, works poorly on Wayland. (Easy fix is to force X11 for QT via QT_QPA_PLATFORM=xcb)
    3. Had some issues with mixed integrated/NVidia graphics on a laptop I was using for a demo once.
    4. Covering or otherwise hiding a Wayland window blocks a program’s graphics thread. This is sometimes problematic.
    5. VR development had issues a while ago? (This was for work. It just… stopped working at some point. Dunno if it was a Linux, SteamVR, or Unity3D issue. My work machine mostly runs Windows 10 now as a result. Oh well.)
    6. Screen recording didn’t work well a while ago… (continued)

    Overall, it’s just worked great though!

    My anti-complaints:

    1. Mixed refresh rates on monitors “just works” now. (I have a 1080@144 for gaming, and a 4k@60 for work)
    2. Video frames don’t have half drawn content. (ex: when resizing windows), except on XWayland stuff
    3. Video tearing has basically disappeared.
    4. Video timing issues seem to be improved.
    5. Input handling for keyboard layouts has improved.
    6. Screen recording in Wayland is way better than it ever was on X11 now. I do this a lot to share gamedev stuff I’m working on.
  •  Russ   ( @russjr08@bitforged.space ) English
    11•6 months ago

    My experience with Nvidia+ Wayland was… Less than desirable. Enough to make me pickup an AMD card.

    However, once I did that my experience instantly better. Hell, even X11 worked better - I was never able to get the desktop to stay at a consistent 60FPS (I’m still on a 60Hz panel which I’m just now getting around to upgrading shortly) in X until I moved to my AMD card.

    The 545 driver update just made things so much worse. So I’d say Wayland+Nvidia is not great (for others it works fine so maybe it’s down to what card you have?) however on my AMD card (and my old MacBook with Intel integrated graphics) it’s fantastic.

  •  cerement   ( @cerement@slrpnk.net ) 
    10•6 months ago

    “not everything is fully ported yet”

    “There will probably be an awkward period before all of these pieces are in place for all of the people.”

    I think these are the two key takeaways – Wayland is still in development and the bandwagoning are the early adopters – most of us will switch when our distros switch (and will probably be none the wiser)

    the problems (and the reason we’re suffering through sensationalist stuff like “Wayland breaks everything!”) is the fanboy push to switch before it’s ready – not everybody lives on the bleeding edge (just like not everyone runs Arch) and the “switch now or be left behind” attitude does more harm than good (far more likely to alienate than convert) …

    •  kingmongoose7877   ( @kingmongoose7877@lemmy.ml ) English
      3•6 months ago

      Wayland is still in development and the bandwagoning are the early adopters

      Not to bust your chops but I’m not sure what you’re implying. What isn’t still in development? WordStar? X11? Mac System 7? And Wayland’s initial release was 2008. That’s 15 years ago. Who are these “early adopters” of which you speak anymore?

      •  kbal   ( @kbal@fedia.io ) 
        3•6 months ago

        Many of those things you’re thinking of were declared Somebody Else’s Problem by said developers. That’s fine, but Wayland was not ready for use by normal end users until somebody else did finish them.

        From what I hear most of them actually are finished by now, but they weren’t as of a couple years ago when it started becoming commonplace to see declarations that the time to switch to Wayland was Right Now. I tried it out then, and am as a result much less enthusiastic about doing it again now even though it’d be much more likely to go well.

      •  drwankingstein   ( @drwankingstein@lemmy.dbzer0.com ) English
        5•6 months ago

        I didnt even remotely imply that x11 doesn’t have issues, so im not sure why that was brought up. The goal is to make wayland an acceptable and universal replacement, Everyone knows x11 is dying but wayland isnt ready to replace it yet

        Things like window embedding, the wayland way is for each app to have it’s own embedded compositor. Wayland has no support for things like overlays/always on top (Useful for OSKs PR has been made but like all wayland things, we might not get it for another couple years, or perhaps never), currently missing support for reading other window states (PR made for this as well, but again, who knows how long it will take), Still no support for window positioning (again PR made), Emulated input events (libei is not universally supported) And these are just the ones off the top of my head, There were others but I cant think of them ATM