And that's how it be with the X Window System.
Compare: Windows Services for Linux.
A file server mediates access to a file system; clients connect to access files. A database server mediates access to a collection of data; clients connect to access data. A print server mediates access to a printer; clients connect to access the printer.
And an X server mediates access to the graphics device; clients connect to access the display and its related peripherals (keyboard, mouse).
If you wanted to do email on your home computer, you'd [buy and] install an email client.
You wanted to go on AOL? Install the AOL client.
Need to use Lotus Notes? Have MIS send a guy over to install the Notes client.
Wanted to run X programs? Install an X server. What? Seemed weird!
You still hear that terminology some, but nowadays you're much more likely to hear about an email app.
Anecdata, but that's why it's confusing to me even today.
Envoy uses the opposite definitions from what I’m used to. And has a perfectly cromulent explanation for why; I’m convinced. But now I don’t know why I started calling them the opposite.
I just envision being Darkly Noon, sitting at the river bed, watching the giant shoe floating into view from upstream, going downstream.
Anything else don't make sense.
That response would then come from downstream from Darkly.
My point was that it's a matter of perspective. And it requires a certain well-defined gradient (the river), I don't think "upstream" and "downstream" make much sense when all you have is a lake.
But as a user, the IO devices that I interact with (keyboard, mouse, display) are the client that connect to some backend (whether a web server or a remote program).
It's the MacOS Classic and GDI and similar direct-to-hw toolkits that are now outliers
I suspect the X terminology is confusing to two groups of people:
1. Those who are used to the idea that when the computer and the display are separated by distance, the local display is a mirror of the remote machine's desktop, courtesy of a service on that machine to which the local display connects as a client. X isn't a remote desktop mirroring protocol, though; those people have the wrong model.
2. Those who are used to the idea that a server is something that runs in the background (daemon), not visible in the desktop. How can the X desktop be the server, when it's shoving pixels in your face, right in the foreground? Well, you know, someone serving you a punch also does it in your face.