• jaxxed@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    The issue with wayland is that both the process and the base mechanisms had significqnt flaws, that made it take a long time to get things working. In all fairness, the core team uad a valiant effort for a dwcade, hampered by unresponsive complainers, and late-to-the-party suggestions.

    Fyi: I am an early WL adopter, but not on any of the major DEs.

    • michaelmrose@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 month ago

      hampered by unresponsive complainer

      How outside of your fantasies did people bitching actually slow down devs introducing features that people should have known were needed in 2008?

      • The Stoned Hacker@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        1 month ago

        Large Wayland projects like KDE and Gnome that are considered member projects of Wayland had the ability to NACK new wayland protocols and proposals. This has historically been abused by a lot of a different projects, in many instamces Gnome because they didn’t want to implement things. A lot of wayland proposals were unnecessarily delayed because of this. The bylaws of how wayland projects are allowed to NACK things has since changed to make it so a single project cannot needlessly block protocols but this was only implemented in the past few years iirc so for a long time this happened. Thats a massive contributor to why wayland development takes so long.