4 ms·
https://medium.com/@donhopkins/the-x-windows-disaster-128d398ebd47 https://medium.com/@donhopkins/the-x-windows-disaster-128d39... The Nongraphical GUI XCalc
by DonHopkins 6y ago
https://medium.com/@donhopkins/the-x-windows-disaster-128d398ebd47 https://medium.com/@donhopkins/the-x-windows-disaster-128d39...
The Nongraphical GUI
XCalc After Several Resizings
https://miro.medium.com/max/434/0*LIDAYbj5NRANRGl7.gif https://miro.medium.com/max/434/0*LIDAYbj5NRANRGl7.gif
X was designed to run three programs: xterm, xload, and xclock. (The idea of a window manager was added as an afterthought, and it shows.) For the first few years of its development at MIT, these were, in fact, the only programs that ran under the window system. Notice that none of these program have any semblance of a graphical user interface (except xclock), only one of these programs implements anything in the way of cut-and-paste (and then, only a single data type is supported), and none of them requires a particularly sophisticated approach to color management. Is it any wonder, then, that these are all areas in which modern X falls down?
Ten years later, most computers running X run just four programs: xterm, xload, xclock, and a window manager. And most xterm windows run Emacs! X has to be the most expensive way ever of popping up an Emacs window. It sure would have been much cheaper and easier to put terminal handling in the kernel where it belongs, rather than forcing people to purchase expensive bitmapped terminals to run character-based applications. On the other hand, then users wouldn’t get all of those ugly fonts. It’s a trade-off.
- SllX 6y agoHere’s a non-Medium version[1], since Medium is similarly but completely unrelatedly, a disaster. [1]http://www.art.net/~hopkins/Don/unix-haters/x-windows/disaster.html http://www.art.net/~hopkins/Don/unix-haters/x-windows/disast...
- gnu8 6y agoThe original UNIXUX site is very clever, but if the guy who actually wrote it is linking to Medium instead, I’m not sure if we can overrule him.
- SllX 6y agoNo one is getting overruled, you now have one additional choice of links to click on for the same material, free of charge.
- DonHopkins 6y agoSadly the unixsux site lost its luster when Netscape disabled the <BLINK>_</BLINK> cursor. http://www.art.net/~hopkins/Don/unix-haters/login.html http://www.art.net/~hopkins/Don/unix-haters/login.html Here's my not-so-subtle Solaris joke about how AT&T was ruining Unix: http://www.art.net/~hopkins/Don/unix-haters/panic.html http://www.art.net/~hopkins/Don/unix-haters/panic.html
- SllX 6y agoI mean clearly the blink tag had to go. It was annoying, unsafe, a blight on the web; not at all like CSS3, JavaScript, WebAssembly and whatever that DRM thing was called, encrypted media extensions, was it? Priorities, man! Thanks for coming out, the X Windows Chapter was my favorite in the book. :)
- DonHopkins 6y agoShameless plug: You could buy a copy of the book! ;) https://www.amazon.com/UNIX-Haters-Handbook-UNIX-Haters-line/dp/1568842031/ref=sr_1_1 https://www.amazon.com/UNIX-Haters-Handbook-UNIX-Haters-line... Or just download the pdf file: https://web.mit.edu/~simsong/www/ugh.pdf https://web.mit.edu/~simsong/www/ugh.pdf
- mcguire 6y agoDon, did you ever figure out the difference between a "client" and a "server"?
- DonHopkins 6y agoSure: xterm a client of your display and keyboard and mouse, remote input and output services that the X11 server provides over the network. And at the same time, a web browser is the client of computing and data servers in the cloud, provided over the network. In reality, there can be many different client/server relationships existing in different directions over the same full duplex network connection. It's really a bi-directional multiplexed messaging channel, not a pure strict hierarchical relationship, and many client/server dependencies can go both ways over the same connection, at the same time. You can even run an ssh that opens tunnels in both directions, then tunnel X and http connections over that. Once a connection is established, it really don't matter which end initiated the connection (or how many links and proxies and tunnels there are along the way) -- you're just sending messages both ways. "Client/Server" is an over-simplified way of describing what's possible.
- ddingus 6y agoOnly the server, actually serves the graphics to the user. Within the context of the X Window System, the server is the body of code responsible for delivering the display to the user viewing it.
- bitwize 6y ago> Only the server, actually serves the graphics to the user. The server actually serves the user to the remote client. It's like "you are not the customer, you are the product". The remote program needs to communicate graphically with you, and connects to the X server to do this; therefore, you are not the requester of a resource, you are the resource being served. :)
- DonHopkins 6y ago
- m463 6y agoI always ran xdaliclock
- kevin_thibedeau 6y agoXterm has popup menus, though I don't know when they were added. I've blown people's minds when they saw them. There's also the Tektronix vector terminal emulation in a separate window. It's also trivial to modernize it with features like scroll wheel support because of the flexibility of X resources.