21 ms·
>X is the graphical interface for essentially all Unix derived desktops (all other competitors [link to Display PostScript wikipedia page] died decades ago). S
by DonHopkins 8y ago
>X is the graphical interface for essentially all Unix derived desktops (all other competitors [link to Display PostScript wikipedia page] died decades ago).
Since when was an X-Windows extension a "competitor" to X? Display PostScript was simply a proprietary X-Windows extension that fell out of fashion, not a competitor to X-Windows.
NeWS was a competitor to X-Windows that died decades ago, but Display PostScript was never a "competitor" to X-Windows, just like the X Rendering Extension and PEX were never competitors, just extensions.
But at least the article gets credit for calling it X-Windows instead of X11, to annoy X fanatics. ;)
https://medium.com/@donhopkins/the-x-windows-disaster-128d398ebd47 https://medium.com/@donhopkins/the-x-windows-disaster-128d39...
- wmf 8y agoDidn't NeXTSTEP use DPS without X?
- DonHopkins 8y agoNeXTSTEP for the NeXT workstation, started in 1987 and released in 1989, used a DPS server with its own protocol without X (the DPS code was licensed from Adobe, the same code that ran in laser printers like Apple's LaserWriter). https://en.wikipedia.org/wiki/Display_PostScript https://en.wikipedia.org/wiki/Display_PostScript In 1985, two years before DPS was started and four years before NeXTSTEP was released, James Gosling and David Rosenthal at Sun developed their own PostScript interpreter for NeWS, originally called SunDew, which was distinct from and quite different than DPS, and wasn't licensed from Adobe. http://www.chilton-computing.org.uk/inf/literature/books/wm/p005.htm http://www.chilton-computing.org.uk/inf/literature/books/wm/... https://en.wikipedia.org/wiki/NeWS https://en.wikipedia.org/wiki/NeWS Then in 1993, NeXT and Sun developed OpenStep for X-Windows/DPS. https://en.wikipedia.org/wiki/OpenStep https://en.wikipedia.org/wiki/OpenStep One of the biggest architectural difference between NeXTSTEP/DPS and NeWS is that NeXTSTEP didn't take advantage of the technique we now call "AJAX," by implementing the user interface toolkit itself in PostScript running in the window server, to increase interactive response and reduce network messages and round trips. https://news.ycombinator.com/item?id=13783967 https://news.ycombinator.com/item?id=13783967 NeXTSTEP wasn't trying to solve the remote desktop problem: the toolkit implemented in Objective C code just happened to be using local networking to talk to the DPS server, but in no way was optimized for slow network connections like NeWS was (and AJAX is). You couldn't run NeXTSTEP applications over a 9600 baud Telebit TrailBlazer modem, but NeWS was great for that. I worked on the UniPress Emacs display driver for NeWS, which was quite usable over a modem, because you do stuff like text selection feedback, switching and dragging multiple tabbed windows around, and popping up and navigating pie menus, all implemented in PostScript running locally in the window server, without any network traffic! https://www.donhopkins.com/home/code/emacs.ps.txt https://www.donhopkins.com/home/code/emacs.ps.txt https://www.youtube.com/watch?v=hhmU2B79EDU https://www.youtube.com/watch?v=hhmU2B79EDU NeWS was architecturally similar to what is now called AJAX, except that NeWS coherently: used PostScript code instead of JavaScript for programming. used PostScript graphics instead of DHTML and CSS for rendering. used PostScript data instead of XML and JSON for data representation.
- erik_seaberg 8y agoI'm not sure what protocol they used for remoting NeXTSTEP's native WindowServer, but I don't think it was X11. Some people did tunnel Display PostScript over X11, but that wasn't the only option and it was pretty kludgy.
- DonHopkins 8y agoThat's right. DPS wasn't used for handling input events, or implementing the user interfaces widgets, which instead were implemented in Objective C running in another client process (usually running on the same machine), instead of PostScript running in the window server. DPS didn't handle events with PostScript in the DPS window server. Instead, it would ping-pong events over the network from the window server, to the Objective C client, then send PostScript drawing commands back to the window server. (Typically generic low level drawing commands, not a high level application specific protocol.) So NeXTSTEP suffered from the same problems of X, with an inefficient low level non-extensible network protocol, slicing the client and server apart at the wrong level, because it didn't leverage its Turing-complete extensibility (now called "AJAX"), and just squandered PostScript for drawing (now called "canvas"). So for example, you couldn't use DPS to implement a visual PostScript debugger the way you could with NeWS, in the same way the Chrome JavaScript debugger is implemented in the same language it's debugging (which makes it easier and higher fidelity). https://medium.com/@donhopkins/the-shape-of-psiber-space-october-1989-19e2dfa4d91e https://medium.com/@donhopkins/the-shape-of-psiber-space-oct... >The Shape of PSIBER Space: PostScript Interactive Bug Eradication Routines — October 1989 >Abstract >The PSIBER Space Deck is an interactive visual user interface to a graphical programming environment, the NeWS window system. It lets you display, manipulate, and navigate the data structures, programs, and processes living in the virtual memory space of NeWS. It is useful as a debugging tool, and as a hands on way to learn about programming in PostScript and NeWS.
- danieldk 8y agoI guess the author is referring to NeXTSTEP and NeWS, which both used DPS.
- DonHopkins 8y agoNeWS definitely didn't use DPS. They were completely different implementations of PostScript, with very different design goals and features.