• SkyeStarfall@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    24
    arrow-down
    1
    ·
    9 months ago

    The whole point of Wayland to be a successor to X11 but not using X, made by the same devs that developed X11 to specifically move away from X. Backporting features would miss the whole point because devs left because adding new features to X was getting too difficult and messy according to them, due to how big and all-encompassing and inter-connected that protocol was.

    And being punished for using Nvidia was Nvidia’s fault, not Wayland’s.

    • Drito@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      arrow-down
      2
      ·
      9 months ago

      made by the same devs that developed X11 to specifically move away from X

      There are probably Xorg maintainers in that project, but I doubt about X11 protocol creators. This is a different thing.

    • PseudoSpock@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      2
      arrow-down
      8
      ·
      9 months ago

      The only proper thing to do was to continue X development. It just needed proper funding and for people to quit battling over licences. Throwing it all out and replacing it with something not even based around network displays was madness. Now we have this hodgepodge of kluges taped together to try and barely imitate what we once had. It’s an embarrassing disgrace.

      • SkyeStarfall@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        7
        ·
        9 months ago

        The “just” there is doing a lot of work considering the devs themselves disagreed. Sorry, but, I’m going to trust their judgement.

        …also the whole networked displays themselves was what caused a lot of problems, according to the devs. Using it for a modern display stack was like trying to fit a round peg in a square hole. Terminals have fallen out of favor ages ago, and personal computing devices today favour things like high responsiveness, clean images, and high refresh rates instead. And we got enough computing power to just stream a video stream directly if that’s needed now.

              • Communist@lemmy.ml
                link
                fedilink
                English
                arrow-up
                5
                ·
                9 months ago

                The spec was the problem, it was awful, again, none of the devs agree with you. The people who deal with this and are experienced with it ALLL chose to move to Wayland development.

                • PseudoSpock@lemmy.dbzer0.com
                  link
                  fedilink
                  arrow-up
                  1
                  arrow-down
                  5
                  ·
                  9 months ago

                  It was more attrition by age. New devs came in and didn’t fully understand it. The XFree86 vs Xorg war only made that problem worse. Those who came later didn’t understand it well enough to continue supporting it. Now you’ve got young devs not understanding why things are important to its design, and of course, they want to rip it all up and start over. They haven’t yet learned the lessons of what made the design choices important.

                  • Communist@lemmy.ml
                    link
                    fedilink
                    English
                    arrow-up
                    4
                    ·
                    9 months ago

                    Don’t you think that if NOBODY understands it and is willing to support it… maybe it’s just fucked?

                    There are no actual issues going on with wayland development, you’re just being a crybaby about network transparency. It’s not even not there, you just don’t like that it was implemented later…