4 ms·
How PostScript kickstarted desktop publishing
- PopAlongKid 4y agoMy first "desktop publishing" experience was using troff on Unix and sending output to the university's phototypsetter. Then, in the second half of the 1980s, I worked at a Fortune 200 company in the team rolling out PCs and networks across the company's many locations. At the time, the basic choice was the HP laserjet with optional font cartridges (which were very expensive as I recall, something like $200 each in 1980s dollars), or the Apple laserwriter which was something like $4K if I recall correctly, but had Postscript built in, so no need for hardware font cartridges. So as a result, the HP hardware got rolled out to most offices where mostly what was needed was to print memos in default monospace font, while to make a nice looking newsletter, flyer, or brochure, you had to travel to headquarters to use the Apple printer.
- the-printer 4y agoI was delighted to discover a full chapter dedicated to troff in a textbook I picked up on Berkeley Unix. Raw documents written in troff (the ones that I’ve seen) seem so quaint. Like little homemade chicken pot pies. I’m mixed on the state of desktop publishing today. I’m missing that quaintness.
- TheOtherHobbes 4y agoI wasn't aware there was a state of desktop publishing today. DTP has mostly been superseded by the web. DIY amateur print of posters and such is more likely to be hammered together in Word than in Indesign. Design agencies still do design-for-print, but there's usually an integrated workflow of some kind which means web and print assets - including styles - can be shared and reused. It's a long way from the blocky output of a 300dpi laser in the early 90s assembled on a PC running a $50 DTP suite. The sad thing about Postscript is that it could have been the foundation of the web, which would have made web and print integration much simpler and design more straightforward and consistent. Instead we got the sprawling incoherent catastrophe that is HTML/CSS/js for the web, PDF for most other document-ish things, and Epub (which is a dumbed down and DRM'd version of HTML etc) for digital book publishing.
- robinsonb5 4y ago> DIY amateur print of posters and such is more likely to be hammered together in Word than in Indesign. Word? I should be so lucky! The bane of my life is people preparing print jobs in Powerpoint!
- digitalsankhara 4y agoPowerpoint! I should me so lucky. I was once passed an Excel spreadsheet where my colleague had layed out a flowchart! True story.
- donbrae 4y agoI once received a website redesign mock-up made in Excel. Ingenious.
- dhosek 4y agoMy first printer was an HP LJ II+ with the PostScript cartridge. I had to buy extra RAM for it and for a while, I had more RAM in my printer than in my computer. A few years later, I bought a fancier PS printer that printed ledger size pages and handled duplex and again I had more RAM in my printer than in my computer. I used to occasionally write PS documents by hand (one was to print out country placards for the Model United Nations club at my college where for country names which were especially long, the text would be auto condensed. These days, with the advent of printing subsystems in the GUI and the fact that software no longer needs to handle the printer directly, I don’t know if anyone ever buys PS printers at all anymore.
- rahimnathwani 4y ago"I don’t know if anyone ever buys PS printers at all anymore." Most IPP-compatible printers accept PDF files. Some also accept postscript and/or PCL. IPP printers advertise their formats with the document-format-supported property.
- dhosek 4y agoPDF, although it can resemble PostScript, is not PostScript. PostScript is a Forth-derived Turing-complete programming language that, in an era of generic printer drivers, offers little benefit anymore since it’s unlikely that an OS printer interface would take advantage of its capabilities. In the old days of programs managing printer output directly, it was handy to be able to do things like decompress TeX PK font bitmaps on the printer (or even more dramatically to send binary data for illustrations to be decoded and decompressed on the printer), but the set of printer primitives that are supported by OS printer APIs is constrained enough that nobody will do these sorts of things anymore. PDF is now essentially the lingua Franca of print interfaces and the programmability of PostScript is more a liability than a benefit.
- kkfx 4y agoPostScript have followed some previous ideas but the most important part is a thing lost in modern software: a programming language to create documents AND applications at the same time. A kind of document UI years after Xerox. Modern publishing software have ditched this approach for another, a fully visually one, formally easier, sometimes easier, but in general limited and limiting.
- orange8 4y agoWhat about HTML?
- kkfx 4y agoHTML is just a markup language, PS is a programming one, NeWS [1] was an X11-alike server PS-based, SUN Pizza Tool a nice demo [2] oh, sure in term of ease of use is a bit awful to write and read, but still it's a "graphics oriented programming language" while HTML just target crafting clickable text with limited extras. [1] https://en.wikipedia.org/wiki/NeWS https://en.wikipedia.org/wiki/NeWS [2] https://donhopkins.medium.com/the-story-of-sun-microsystems-pizzatool-2a7992b4c797 https://donhopkins.medium.com/the-story-of-sun-microsystems-...
- digitalsankhara 4y agoInteresting. So NeWS was like display postscript? Which I think was also used in NeXT OS.
- the-printer 4y agoFor more discussion from an earlier iteration of this article: https://news.ycombinator.com/item?id=33820907 https://news.ycombinator.com/item?id=33820907
- gumby 4y agoI was disappointed when Postscript was initially released, as they were at pains to port the constraints of paper to the computer, which I considered (and still consider) a gross step backwards. Display postscript (Sun and NeXT mostly) was an improvement but documents were still stuck in a paperish mode. Few PDF are truly editable. This was made much worse when displays migrated from portait by default to landscape by default. Even today my heart sinks when I see that I've been given a pdf
- User23 4y agoPostscript was solving the problem of producing nice proofs for photo transfer. Complaining about how it's not a great display protocol on modern flatscreens isn't missing the point, it's not even realizing there is a point to be missed.
- gumby 4y agoThat’s not how it was marketed. I used the Dover and its postscript predecessor (I can’t remember the name) so I’m familiar with the page description languages described in the article (I was at PARC for a while). PDF was supposed to go beyond that, and its parametric model was a conceptual win…then mostly constrained as a semantic-free rendering system.
- massysett 4y agoAs bad as a PDF is, it's even worse to get a Word document. Now, imagine saving that Word document and trying to open it twenty years from now.
- blacksmith_tb 4y agoHmm, yes and no. If you want to be able to edit more than a single word or two, I'd rather have the Word doc, it can at least handle wrapping text, widow control etc. (even if the format is a moving target and even MS can't seem to always handle it... so yes, in 20yr you'll need to do your edits via DOSBox). If you only need to read it, PDF wins certainly.
- 4y ago
- jmbwell 4y agoEarly in my career, I worked at a newspaper. Pages were laid out by literally cutting pieces of paper and gluing them (with semi-adhesive wax) onto big sheets of paper. Sometimes on a backlit table, so you could see what the camera would see. Then it was shot with a huge camera. The remainder of the process was messy and entirely mechanical. “Desktop publishing” changed ALL of that. And now, we just call it “print.” Postscript’s contribution to this transformation can hardly be overstated. To have a language for describing a printed page that could be exchanged between all the disparate systems of the 90s, …it was a revolution.
- Hard_Space 4y ago> Pages were laid out by literally cutting pieces of paper and gluing them Cow Gum, it was called in the UK (I don't know about elsewhere). I was a graphic designer in the late 1980s, and remember all that analog equipment, including Rotring pens (insanely expensive) and line tape, and photomechanical transfers (PMTs). Today is better.
- cafard 4y agoYes, a revolution. For those who never saw the old ways, https://journoterrorist.com/2011/08/02/paperball2/ https://journoterrorist.com/2011/08/02/paperball2/ gives an entertaining picture.
- saagarjha 4y agoKind of sad to see PostScript slowly fade away these days. My Mac won’t even open .ps files anymore! The entire graphics stack was designed around it and they removed viewer support for it…
- randomdata 4y ago> The entire graphics stack was designed around it and they removed viewer support for it… NeXTSTEP was built on Display Postscript, but macOS's graphic system is modelled after PDF.
- gpvos 4y agoThe graphics model of PS and PDF is essentially the same.
- randomdata 4y agoEssentially, except (D)PS is executable. Quartz is not built around that model.
- deleted 4y ago[deleted]
- NorSoulx 4y agoBack in early 90s I was working for a big international company using VAX servers and DEC laser printers in their engineering department. The wanted to have various types of graphical reports outputted based on data in their INGRES database. To produce those graphical reports I used FORTRAN and hand-written PostScript code. Did a fair amount of PostScript coding back then. Remember I purchased a set of PostScript books to study. I still have them in my library: https://coding-and-computers.blogspot.com/2022/12/postscript-coding-for-vaxvms-system-in.html https://coding-and-computers.blogspot.com/2022/12/postscript...
- jtotheh 4y agoI own a color Postscript laser printer (HP) that cost me about $400. That blows my mind.