Skip Navigation

You're viewing part of a thread.

Show Context
124 comments

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

    • 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?

      • Being able to remotely display apps from other servers and workstations is important. Games? Not at all.

        • 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...?

          • 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.

            • 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.

              • It was the core of why X Windows was so much better than Windows.

                • No, it was just a neat little extra feature.

                  It's also a feature that exists in wayland.

                  • 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.

                    • 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?

                      • 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.

124 comments