Originally Posted by
John Coloccia
Several years ago, I was managing/developing a software effort out in California. The servers we were developing on were in San Jose. Most of my team was in Lancaster, CA. Occasionally, we were in Wichita, KS. Another core member of the team was in Boston. We ROUTINELY (i.e. everyday, all day) used X remotely, over a VPN connection no less, with no issues whatsoever.
Not only that, but people ROUTINELY use X in this way, day in and day out. They do things like run their processor intensive software on the mega-machine in the corner, logged in from a remote terminal. Not only does it work, it works seamlessly, and has no equal in the industry. We have been doing this for DECADES and it is a perfectly normal, everyday occurrence as natural as getting your morning cup of coffee. It was designed specifically to do this back when it was common to have a mega-server doing real work, and terminals scattered about controlling the show. This is the typical use of X, not he exception. It's only now that Linux has become popular that the standalone Unix-like workstation has become the norm. In the world of engineering and science, it would be very unusual to have standalone workstations. You most typically several powerful workstations scattered about with less powerful workstations sitting on most people's desks. Again, this is typical, not the exception.
Because X is socket based, it is entirely platform independent. As long as the platform supports sockets, an XServer can be written for it and it can interact with any program on the planet that supports X. It doesn't matter if the server is a Unix machine and the client is a PC, MAC, smartphone or WHATEVER. I can access any machine in the world from any other machine in the world. More, it is common for the terminal to be running multiple applications on multiple servers, in remote locations or not. This is perfectly normal in the Unix world.
Further, X predates Windows by a couple of years, as does the Macintosh GUI. It has absolutely nothing to do with KDE or Gnome, nor does it have ANYTHING to do with what your mouse buttons do or any other behavior. In fact, the X Server knows nothing at all about what window manager you happen to be using on your end. It's no problem for one user to be logged in using KDE while another user across the world is logged in using OpenWindows, and someone else is logged in using FVWM. It makes no difference at all. It is the local window manager that defines the look and feel of the GUI, including what your mouse buttons do, not X. This is part of the design philosophy of X.
I'm also confused at the link between KDE, Qt and Gnome. KDE was based on Qt, which was not free at the time. KDE doesn't "own" Qt, and can't decide anything about it. Qt is a Nokia product (was a Trolltech product). Gnome was started because some weren't happy with KDE being based on a non-free (free as in "liberated") product. Since 2005, QT has been available under GPL licensing, making this entire issue moot. LGPL licensing just makes QT and KDE more attractive to commercial customers, but GPL fixed the major philosophical gripe that sparked the Gnome project.