Wayland. It comes up a lot: “Bug X fixed in the Plasma Wayland session.” “The Plasma Wayland session has now gained support for feature Y.” And it’s in the news quite …

  • thalience@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    Then the problem is that it’s abandoned, not that it has stagnated

    By all means, feel free to start working on it!

    All the people who developed Xorg for 20+ years decided that creating and working on Wayland was a better use of their time. But I’m sure you know better…

    The problem isn’t that Xorg is spaghetti code (it’s pretty good for a large C project, imho). The problem is that the X11 protocol was designed to expose the capabilities of 1980s display hardware.

    • BaumGeist@lemmy.ml
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      1 year ago

      Stop putting words in my mouth. I never mentioned spaghetti code, and i said nothing about being better or smarter than either Xorg or Wayland devs

      • thalience@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        You said that Xorg being abandoned is the problem. How should we interpret that, other than a criticism of the decision-making process of the devs?

    • Kristof12@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Wayland will become a spaghetti too, unless you do “compositorhop” because one compositor is not complete and need to use another, idk if this would be a good idea