Wayland is great! Except for all list of not-a-bugs that I'd like to see fixed. Still, I'm not going back to X, so take that how you will.
What are the not-a-bugs? Things like covering up a Wayland window will block it's rendering thread indefinitely with no way to detect it happens to handle it. This can lock up some games, or cause you to time out in a networked application. Some Wayland core folks don't want applications to know if their window is visible or not because it's mild information about a user's attention that should be private. Every game dev on the other hand is asking "WTF!?" as it causes their games to break randomly.
Another mild example is that windows cannot be raised except by the user or by launching them. This is supposed to be a mild security precaution so a program can't pop up a legitimate looking dialog over another application and trick the user. Realistically it means that applications can't open and focus URL in your web or file browser. Instead they have to give you a notification telling you "Firefox is Ready" and make you do it manually.
A lot of this is slowly (painfully?) changing, and the adversarial nature is a bit frustrating. Wayland fixes so many little things that I find it well worth it though, and I say that as a game developer frustrated by many of the core design decisions.
People keep saying this, but X forwarding seems to work just fine with XWayland. I just tried a handfull of X programs between my machines, and neither are running X11. I don't use it everyday to know the gotchas, but there you go. Programs that use shared memory pixel buffers (everything that isn't xeyes realistically) even run better than I remember now that I have gigabit. >_< It's still a way worse experience than VNC or RDP though.