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.
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.
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.
Wayland needed that core functionality from the start.
No it didn’t.
They chose not to include it, it was so short sighted.
They chose to make it an add-on to the protocol, this harms literally nothing except your feelings.
That’s why waypipe was created, to cover the huge gap they created.
…Yes, people made waypipe because waypipe didn’t exist yet, now it exists, and it works fine.
and by the time someone glued that hack onto the side of wayland, it was too late
Too late for… your feelings?
It was already hated for neglecting the primary use of X windows
Nobody but you thinks that’s 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.
…Are you not aware of what the wayland devs have been doing? they add features and implement them, they didn’t do it all instantly from the start because that’s literally impossible. It now has all the missing features.
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.
This is nonsense, give me an actual example of how waypipe is worse, network transparency was sacrificed to work on more important features, and made it easy to extend the protocol to support it later. There’s no downsides to this.
That will never be as elegant and pure as a fully integrated built in solution.
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.
No it didn’t.
They chose to make it an add-on to the protocol, this harms literally nothing except your feelings.
…Yes, people made waypipe because waypipe didn’t exist yet, now it exists, and it works fine.
Too late for… your feelings?
Nobody but you thinks that’s the primary use of X windows.
…Are you not aware of what the wayland devs have been doing? they add features and implement them, they didn’t do it all instantly from the start because that’s literally impossible. It now has all the missing features.
This is nonsense, give me an actual example of how waypipe is worse, network transparency was sacrificed to work on more important features, and made it easy to extend the protocol to support it later. There’s no downsides to this.
It already is.