5 ms·
Reading this post, it strikes me that there could have been standalone monitors with an Ethernet port that had just enough compute power to run an X server.
by jandrese 6y ago
Reading this post, it strikes me that there could have been standalone monitors with an Ethernet port that had just enough compute power to run an X server.
- PAPPPmAc 6y agoThere were. They were called X terminals ( https://en.wikipedia.org/wiki/X_terminal https://en.wikipedia.org/wiki/X_terminal ) and there were quite a few of them on the market around the early 90s, supplanting the traditional terminal protocols. Then there were quite a number of Thin Client ( https://en.wikipedia.org/wiki/Thin_client https://en.wikipedia.org/wiki/Thin_client ) devices that were a hair more independent than dumb X terminals, from players like Sun (Sun Ray) and Wyse (Now part of Dell). There was an inversion from "Users per to Computer" to "Computers per User" and that model mostly fell out of favor.
- erik_seaberg 6y agoThere are third-party X servers for Windows, but almost nobody has heard of them, while everyone has a browser. So we’re abusing Javascript and HTML to replace X as a remote UI protocol for desktops/laptops that barely have any installed software.
- sergeykish 6y agoX application draws on X Server, imagine server drawing on <canvas> over websocket. Each character I type would be handled by server. I can't imagine hardware requirements for HN in this model. NeWS is a better comparison to web browser.
- GekkePrutser 6y agoYes and those X-Terminals were exactly what X was invented for. This is why the net transparency is not great over high-latency connections, it was never designed for that. In those days companies only had a handful of "computers" and people worked on terminals. Usually shared over a 10 megabit shared ethernet bus, which was surprisingly responsive! However they were more than a simple terminal. Most of them were basically small Unix computers (like the SPARC X-terminal which was just a diskless low-powered SPARCstation, it could actually run full Solaris). HP's EnvizeX stuff was similarly complex though I don't think they could run HP-UX. But they weren't nearly as 'dumb' as the text terminals of the days. I still have a few Sun Rays here but they used a very different protocol that only worked with their proprietary software. However I do expect a return of this model. Now with the cloud, a lot of computing is once again shifting to a central model rather than on the endpoint.
- Koshkin 6y agoA Raspberry Pi 1 makes for a good X terminal.
- jlokier 6y agoThere were, and they worked very well. I used them for a while. You could sit down at any of the terminals on campus, select the server you wanted to log into, and log into your own account. It would bring up a fresh instance of your desktop, much like when you boot up your own computer. Except all the files and configuration were on a shared server. The experience was almost as good as running applications locally, with the added benefit that the applications ran on a big, shared, beefy computer somewhere else, much more powerful than could be placed at each desk. And you could sit down wherever was convenient to do your work, and have all your files and familiar configuration available. Back then, most people didn't have their own laptop to work with so that wasn't an option. Those that did, their laptop would be much slower and have a poorer quality screen.
- GekkePrutser 6y agoYou're right, this is how I studied computer science. A laptop was simply unaffordable for a student in those days (mid-90s). I remember one of my friends bought an IBM "Butterfly" laptop really cheaply at an auction. We were all amazed at it. Imagine, your own computer in your backpack! :D
- shirro 6y agoTypical X terminals ran xclock and xterm back in the day and not much else. Pretty cool for the time though. I remember lan gaming with friends in the 90s sometimes turned into hacking sessions. I would sometimes have a few Mosaic browsers run remotely off my system over 10Base2. Given how slow the dialup modem was downloading html X wasn't the bottle neck. Todays modern desktops with compositing and rendering libraries that can target hardware acceleration and run games and visualisation software on opengl or vulkan aren't well served by network transparency and the X extension model. The sad truth about X network transparency is that it generally worked better to write to a local screen and then send the screen updates over some other protocol like vnc or nx.