• michaelmrose@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    21 hours 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?

    • jaxxed@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      20 hours ago

      I think you have the wrong tone.

      The comainers were nvidia, when they didn’t participate in the early anni g, and then cam in late trying to push a rewrite to the memory sharing model.

      Was that just my fantasy, or did other people have the same drean? I did mention that I was an early adotper. Maybe I should have clarified that I never went back.

      Listen, no matter your opinion on wayland, you can admit that some technical decisions made were not optimal.

    • The Stoned Hacker@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      17 hours 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.