Wayland is a local display server. It's like asking whether the Linux kernel supports ssh. Sure, if someone writes it, but it's not in the scope of kernel development.
Posted Oct 24, 2012 17:03 UTC (Wed) by wmf (guest, #33791)
[Link]
Writing a pedantically-correct FAQ that encourages misunderstandings is a good way to FUD your own project. It should say something like "Remoting is out of scope for the Wayland protocol or Weston compositor, but this will be solved with a proxy that will be bundled with your distro and will Just Workâ˘".
Wayland and Weston 1.0 released
Posted Oct 24, 2012 17:07 UTC (Wed) by wmf (guest, #33791)
[Link]
I hate to respond to myself, but I looked at the actual Wayland FAQ and it's not as bad as the quote above implies, but it's still pretty confusing.
FAQ could be more helpful
Posted Oct 25, 2012 4:28 UTC (Thu) by amtota (guest, #4012)
[Link]
I agree, although I am biased as I maintain xpra.org, I would have expected the Wayland devs to get in touch with us or at least provide a link for those who do want to keep network transparency. Oh well.
Wayland and Weston 1.0 released
Posted Oct 26, 2012 0:17 UTC (Fri) by jschrod (subscriber, #1646)
[Link]
Ah, the systemd argument.
We're replacing "XYZ" that does "ABC", calling it "xyzzy". Believe us, we're doing best work ever, you won't notice anything, and we'll all live happily ever after.
But, "XYZ" does "DEF" as well. How shall we do it in the future?
Well, "DEF" is not the scope of our replacement. It doesn't belong to "xyzzy".
But... "XYZ" did it...
You don't understand: We define the scope. And we're in the position to tell you that while "ABC" might be of interest to you, all the rest of the world doesn't care. So we define that "ABC" wasn't part of "XYZ" and we don't have to replace it.
But... "XYZ" did "ABC"...
As we said, we don't care. We define, you don't need "ABC".
But then... "XYZ" is not a replacement if it doesn't deliver the same functionality.
You're wrong. You're not in the position to define that. We have the power to define what is a replacement and what is not. And we tell you: "xyzzy" is a full replacement for "XYZ", for all relevant functionality. A maze of twisty little passages, all alike.
The story of the Linux desktop,
Joachim
PS: Chosing the name "xyzzy" as illustration is clearly not correct, as it doesn't support remoting to "Y2", even though it should. But, maybe, sometime in the future we'll be able to kill the dragon (aka we'll be able to really replace X) with our bare hands.
Wayland and Weston 1.0 released
Posted Oct 26, 2012 8:17 UTC (Fri) by dgm (subscriber, #49227)
[Link]
> We're replacing "XYZ" that does "ABC", calling it "xyzzy".
Strawman. Wayland does not replace X11. X11 can be run on top of Wayland, just like it does on Windows or OSX. The rest of the argument does not make sense.
Wayland and Weston 1.0 released
Posted Oct 26, 2012 8:25 UTC (Fri) by jschrod (subscriber, #1646)
[Link]
> Wayland does not replace X11.
When Qt und GTK focus on Wayland, these DEs will have native Wayland applications, and X will not be a first class citizen any more. It will only be supported as an legacy interface. As long as we don't want to be stuck using current software versions, that means that de-facto Wayland *will* replace X11 in the medium-to-long term.
Besides, the experience of running X11 on Windows or OS X is no good advertisement, either. I've done both, and good integrated support is something different.
Wayland and Weston 1.0 released
Posted Oct 26, 2012 9:32 UTC (Fri) by paulj (subscriber, #341)
[Link]
This is rubbish. Qt and GTK are not DEs, but toolkits. Further, these toolkits *both* have long supported rendering outputs *other* than X11 for a long time (from Windows GDI to direct framebuffers, even HTML). So there's just no basis to say that the addition of another rendering context, Wayland, is going to change the quality of X11 support.
The only thing that could change that is if X11 becomes so little used that no one cares to support it anymore.