• Communist@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      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
        2
        ·
        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
          2
          ·
          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.

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

              No, it was just a neat little extra feature.

              It’s also a feature that exists in wayland.

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

                Don’t say that. It is not in wayland. That is waypipe, the kluge written to overcome the shortcoming of wayland. They are not the same thing, and it’s disingenuous for you to say so.

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

                  It’s not kludge, and that’s how it should’ve been implemented.

                  It isn’t a shortcoming of Wayland that the core protocol is small, that’s a benefit.

                  Can you actually say what’s wrong with waypipe?

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

                    Wayland needed that core functionality from the start. They chose not to include it, it was so short sighted. That’s why waypipe was created, to cover the huge gap they created. It came too late, it didn’t support remote windowing, and by the time someone glued that hack onto the side of wayland, it was too late. It was already hated for neglecting the primary use of X windows. That hate doesn’t go away unless they internalize the functionality into wayland itself, and take significant steps toward re-implementing all the features of X they ignored and turn it into a real X12. X12 doesn’t have to be from X11 code base, but it does need to do all X11 did, and more, and fully support X11 apps, natively, inside wayland itself, not through Frankensteinian bolted on the side hacks. I’ve said what’s wrong with waypipe a few times now. It’s an ADD ON. Think Firefox extension or plug-in. Not properly included in the original base product, but added on by others. That will never be as elegant and pure as a fully integrated built in solution. Waypipe only exists because wayland was purposefully made incomplete.