• PseudoSpock@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      arrow-down
      3
      ·
      1 year ago

      It’s an add on, not part of the main spec. That functionality should be the most important core piece, not an afterthought.

      • Communist@lemmy.ml
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        1
        ·
        edit-2
        1 year ago

        No, it should be an afterthought. It’s not important at all, it’s a niche weird use case. I care way more about having a functional desktop and everything else. I’m very glad it was treated as an afterthought, because I care more about literally every other feature.

        Tell me why it being an afterthought matters exactly?

          • Communist@lemmy.ml
            link
            fedilink
            English
            arrow-up
            5
            ·
            1 year ago

            It’s important to your specific niche usecase, maybe.

            I’ve never needed to use network transparency, I don’t know anyone who has ever needed to use network transparency, and even if I did, i’d use waypipe… so…?

            • PseudoSpock@lemmy.dbzer0.com
              link
              fedilink
              arrow-up
              1
              arrow-down
              4
              ·
              1 year ago

              Great, you don’t use it. I see it in use all over in my company, and in a couple others. It is an important core functionality. That the wayland devs ignored the use case at all to the point of other devs writing wapipe to overcome their screw up is huge.

              • Communist@lemmy.ml
                link
                fedilink
                English
                arrow-up
                3
                ·
                1 year ago

                That’s not even a screwup, it’s been added, you’re just crying because you think your usecase is the most important for some reason.