> Erm... Wayland applications do NOT depend on the compositor.
You must be talking about some theoretical Wayland again. Real world applications have to use compositor-specific interfaces. For example how are you going to take a screenshot without depending on the compositor? How are you going to make a taskbar without using compositor extension?
> ROTFL. As if X Windows has exactly one compositor and window manager.
That's the point! Single X window system implementation has many WMs. But every single Wayland compositor implementation has just one WM. By design. Encouraged by Wayland. You do know that Wayland server is called "compositor", don't you?
> Yeah, I see tearing in X Windows.
That was an optical illusion. And it was under Wayland. :)
Really, get back to the real life, and at least check RebeccaBlackOS LiveCD to actually see that Wayland you're talking about.
> Indirectly - everyone. Directly - developers who can now write better applications with better graphics stack.
What developers? Developers of what? Developers using toolkits aren't supposed to see any changes. So no benefits for them. Developers of those toolkits just got more work to do, which obviously no good for them too, unless they like to work a lot. Then what developers are you talking about?