" You have no idea what "network transparency" really means."
No... you don't.
Me*: Network transparency means that applications can render graphics to a local terminal or over a network with zero changes in code path and zero need to know anything about the underlying rendering model. Therefore, any remotely modern version of X.org is by definition not network transparent since every since modern local rendering technique such as DRI and compositing is completely incompatible with the fallback socket-based path that is used for networking remote X programs. Consequently, modern X is not network transparent and people who can't understand that just because it is still possible to send X pixmaps over a network socket in a kludgy manner does not mean X is "transparent" should maybe do some research on how X actually works instead of hurling insults.
Modern X-remoting is effectively pushing pixmaps over a socket in an inefficient manner. It is fundamentally different than the modern composited rendering path that effectively bypasses 99.9% of the original X server and is where Wayland is going. Additionally, if X were so beautifully perfect at network transparency then using it over a WAN connection wouldn't be one of the leading causes of suicide in network administrators and proxies like NX would never have come into existence.
Where "Me" includes the X.org developers including Keith Packard BTW.
You: "I MADE PRETTY PICTURES GO OVAR INTARNETS!! DARR!! NETWORK TRANSPARENT! SINCE SOME TYPES OF RDP ONLY TRANSFER DESKTOPS NOT INVIDUAL WINDOWS RDP NOT NETWORK TRANSPARENT!! DAR!!! X DEVELOPERS ARE STOOPID AND DON'T KNOW ANYTHING ABOUT X!!! DAR!!"