It does, because it explains why this change has to be done by VNC client/server devs, and can’t be done in the wayland protocol or compositor.
If a new replacement would have the exact same set of supported use cases as the original, it wouldn’t be useful. The point of wayland is that it enables some new use cases, while restricting some older ones.
Wayland is still powerful enough to implement VNC (weston supports RDP in both directions) or xclip (KDE’s klipper works just fine under wayland). It just requires effort from third parties.
If a new replacement would have the exact same set of supported use cases as the original, it wouldn’t be useful. The point of wayland is that it enables some new use cases, while restricting some older ones.
Wayland is still powerful enough to implement VNC (weston supports RDP in both directions) or xclip (KDE’s klipper works just fine under wayland). It just requires effort from third parties.