On 02/11/17 06:32, Ahem A Rivet's Shot so wittily quipped:
>  Wayland retains the hardware independence but throws away the
> network transparency, which almost certainly makes for a local display that
> performs better than X can.

and Wayland removes the ability to run a GUI application on the RPi
while displaying it on another computer that's connected via a network
cable, something that _I_ do a _LOT_ on headless systems.  I want to be
able to connect my RPi via ethernet ONLY, no keyboard, no mouse, no
video.  Just the ethernet.  And from here, I can program it to do
_anything_.  And being able to run 'pluma' to edit system files, shell
scripts, python code, and so on *LOCALLY* on the RPi is a *HUGE*
benefit.  Wayland takes ALL of that AWAY.

some of the BEST feature of the RPi surface when you run it as a
HEADLESS system, and for that, running GUI applications over the
ethernet is a HUGE benefit.

FYI - if you haven't tried it, here's how it works:

let's say your desktop computer is 192.168.1.50, and the RPi is
192.168.1.51 .

(on the RPI from a secure shell)
export DISPLAY=192.168.1.50:0.0

(on 'your desktop computer' running the X11 server)
xhost +192.168.1.51

(you may need to alter the X11 config a bit to make sure you can access
X11 on the network; check for port 6001 listening on your desktop
machine, and don't expose it to the outside world, i.e. block it at the
firewall)


then run an application like 'pluma' or even a web client like 'midori'.
 It will display on the desktop computer, and interact with the
keyboard/mouse there.  Enjoy!

--- SoupGate-Win32 v1.05