May be about to join systemd as the new tech for graybeards to scorn... but adopt anyway
  • @simpleEnglish
    25•1 year ago

    I’ve been hearing that for like 7 years now

      • lemmyvoreEnglish
        12•1 year ago

        If Wayland is to replace X it needs to provide feature parity and fix what’s wrong with X on top.

        There’s more to being a standard than a reduced feature set that just happens to scratch an itch here and there for some users.

        Pretending that 80% of desktop users don’t exist is not helping either.

        • @[email protected]English
          6•1 year ago

          Of course, but wayland is a solid design that’s on the path towards being that. Development would probably go a lot faster if major distros shipped wayland by default. But because of nvidia, they can’t.

            • lemmyvoreEnglish
              3•1 year ago

              There’s a bit of a jump from “feature complete and still issuing maintenance releases” to “abandonware”.

                • @[email protected]English
                  1•1 year ago

                  I’m just annoyed by the apparent assumption from people promoting messages like this that Wayland is ready for desktop use when it’s not. It seems to give the impression that there aren’t things that have to be fixed. Like how DPI in Firefox is broken, or how MS Teams and other screen sharing apps don’t work.

                  I’ve wanted to adopt Wayland for years but still can’t. Claims like the OP makes it sound as if devs are out of touch with the reality of their users and that’s frustrating. If they abandon X and don’t fix the problems with Wayland then I’m screwed.

        • @[email protected]English
          1•1 year ago

          Besides app support what is missing in wayland(I do not game so I don’t care if the screen is allowed to tear or not)

          • lemmyvoreEnglish
            2•1 year ago

            biggest ones I see:

            • No stuff like autokey, xmodmap, xinput etc. basically no mouse and keyboard customization and no plans to fix it.
            • Issues with non-window overlayed widgets (context menus, modal windows-in-windows etc.)
            • Completely ignores compatibility with the vast majority of desktop environments except a couple, with anything non-Linux, with proprietary drivers etc.

            There’s a general feeling that Wayland is doing you a favor and that anything it breaks is someone else’s problem, that we’re supposed to ignore everything that’s missing or malfunctioning or incomplete and just rejoice at the fact it works in very particular circumstances.

              • lemmyvoreEnglish
                2•1 year ago

                Look, I’m fully familiar with the “scratch an itch” approach to software development in FOSS… I’m not demanding anything from Wayland, I’m just saying it needs to work with the larger software ecosystem. You can’t use a graphical server by itself.

                If it’s not working with desktop environments, not working with Nvidia, not working with keyboard/mouse configuration, not working with the clipboard, having issues with common software like browsers etc… what am I supposed to do about it?

          • @Reliant1087English
            1•1 year ago

            As someone who has made the switch for an year or so:

            • Legacy apps with xwayland do not scale properly and appear blurry and pixelated on my multi-monitor setup. This sucks because there are a lot of old apps that aren’t ported.
            • No great onscreen keyboard that works well.
            • Problems with Java apps like webstorm and pycharm where they won’t scale properly and are unusuable.
            • Even my IDE (code) and other electron based apps glitch sometimes.

            I like Wayland so far but these have been really bothersome.

  • @[email protected]
    4•1 year ago

    wait it hasn’t already? I thought most of the popular distributions adopted it as standard already making the majority of desktop users Wayland users