• Kawawete
    link
    fedilink
    arrow-up
    35
    arrow-down
    12
    ·
    20 days ago

    Accelerating wayland développement would mean forking it. As it is right now there’s a lot of yapping in their git for every decision, small or big.

    • Damage@feddit.it
      link
      fedilink
      arrow-up
      19
      ·
      20 days ago

      Accelerating wayland développement would mean forking it.

      You mean feurking

    • CrabAndBroom@lemmy.ml
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      2
      ·
      20 days ago

      I’d be fine with switching over to Valve’s crazy high-speed frog version of Wayland if it came down to it lol

      • priapus@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        20 days ago

        Wayland is a protocol used by each desktop that supports it. It often moves slowly because each desktop works together and discusses each change. If valve forked it, they would just have a protocol nobody is using. If people started using it, it would just slow down again for the same reason.

        • Gibibit@lemmy.world
          link
          fedilink
          arrow-up
          6
          ·
          20 days ago

          If noone used it that wouldn’t matter. Experimentally implemented features on a separate branch can still be useful as proof of concept to whoever is taking their time to discuss where Wayland has to go. Of course the usefulness depends on how well the Valve devs understand the needs of the desktops.

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        2
        ·
        20 days ago

        That’s how you get fragmentation and instability. Then something is changed it needs to be implemented and then tested by all the desktops. If you move to fast you get ahead of development and testing which is very bad

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      20 days ago

      The thing to keep in mind is that it is a protocol. When something is merged all downstream projects must implement it.