> But Wayland (protocol) is useless without compositor (Weston). You can't write real applications without using compositor extensions.
Erm... Wayland applications do NOT depend on the compositor. They might want to use advisory "window state" interfaces.
> KDE added Wayland support to kwin (that wasn't hard) and it's incompatible with Weston. That's one of the key Wayland problems: it encourages people to write multiple incompatible compositors, so we may end up with many different compositors, and no usable ones.
ROTFL. As if X Windows has exactly one compositor and window manager.
>Have you seen Wayland/Weston yet? Download RebeccaBlackOS, boot it in native Weston mode and try resizing some windows. Then reboot it into KDE+Xorg (it starts in compositing mode by default) and try resizing the very same windows. See any difference? Except KDE being faster?
Yeah, I see tearing in X Windows.
> My question still stands. If Wayland (is it horse or RAV4?) is so good and has so many features, then where are those roads? Who is supposed to feel the benefits of Wayland?
Indirectly - everyone. Directly - developers who can now write better applications with better graphics stack. It's happening already.