The x server is the gatekeeper of X terminals. We aren't playing the game the temple of doom, and we would not like to scare you either but it's fantastic, or you can have a lot of fun with it as well. Do you know those old-timey phones that people used to talk into? Imagine one of those, but with a monitor instead of a handset. Now imagine that monitor is connected to your computer, and you can run programs and interact with your computer in all sorts of ways, just like a phone allows you to talk through the internet. The X server is like that, but for graphics instead of voice. It manages the X clients and does the actual work of managing input and display devices and performing requested operations. This simplifies programming, as the application programs do not need to be aware of the hardware details and rely entirely on the X server. The X server manages X clients, but the relationship is reversed compared to traditional client-server model applications. In conventional client-server implementations, the user of the client requests data from the server, which then displays them on the user's screen through the client. In the case of the X system, however, the user controls the server to retain clients residing in remote workstations so that multiple clients can be held at once, providing the user with different applications running on other machines. This way, more tasks can be done without slowing down the user's device. The display is not merely a window into a single machine's resources. Instead, it is a window into all connected machines' resources and applications, making it possible for several users to work on different projects simultaneously without waiting for one another or interfering with each other's work.