3 ms·

The legacy cruft is easily served by not loading the respective crufty modules. And frankly, I like Xserver support across a variety of devices.

• yellowapple 12y ago
  The problem is that the legacy cruft is intertwined in the very architecture of X11 itself. That's what Wayland is intended to correct; it's a redesign to better accommodate things like compositors while not being held back by the need to explicitly support 80's-era graphical terminals and such (though similar functionality should still be possible, since Wayland is - IIRC - network-transparent).
  • sp332 12y ago
    Wayland is not network transparent. They say it's "out of scope". You'll have to use something like RDP. http://wayland.freedesktop.org/faq.html#heading_toc_j_8 http://wayland.freedesktop.org/faq.html#heading_toc_j_8
    • zanny 12y ago
      The X network transparency is already hugely inefficient compared to RDP or VNC. I also really hope when Dalaa 1.0 comes out (soon, please?) someone starts an initiative to make first class networked display / video streaming a reality on it. You don't really need a new protocol, just vnc-dalaa or rdp-dalaa rather than pixel buffer updates. See how Steam / Nvidia streaming works, or Miracast, except substitute hardware accelerated h264 with opencl accelerated Dalaa for a nice open standard.
      • sp332 12y ago
        The issue for me is that I'll need a working video driver and framebuffer on the remote device, whereas with X I only need to set those up on the viewing end. Theoretically, someone could make a Wayland server that didn't render locally, but no one has made one of those yet.