I think with wayland, the issue goes deeper, as there's a fundamental disagreement about what a display server should do. That's not only about network functionality (you can debate about that indeed, I don't think it hurts to include it, but whatever), but in the wayland thinking, the job of the display server is really nothing but "compositing" clients' windows together (and delivering the most basic input events). NO room for any server-side rendering, for window managers, for any communication between clients, etc pp. The result is that clients need a massive stack of supporting libraries, they MUST do their rendering locally, even draw their own window decorations, agree on some external communication mechanism about basic things like clipboard, and so on. I don't agree with that design at all, of course there are types of applications where it's the best choice to do everything client-side, but the vast majority of regular desktop applications could profit a lot from more functionality offered by the display server as in X.
