Hacker News new | past | comments | ask | show | jobs | submit login
PostScript and Interpress: A Comparison (1985) (mostlycolor.ch)
20 points by com 6 days ago | hide | past | favorite | 7 comments





I’m one of the few people who has written a lot of Interpress (for the Xerox Star) and was responsible for making it work on a number of Xerox printers all implementing a different subsets mostly because it was evolving protocol which different printers shipping on differing schedules.

This is a long paper that I think has too much detail and it obscures the few key important things:

- Postscript is really a general purpose programming language where interpress is rather restricted.

- Interpress was very concerned from the start about being fast to process on the fastest Xerox printers at the time (a 9700 120PPM) and page independence was critical. Wanted to print forward, backward, in the middle without executing the entire file as postscript required. Interpress could easily index the pages and just start printing from any where. Not so with PostScript.

- both had near identical imaging models. It’s obvious why from that article.

- Postscript had a robust scalable font mechanism where-as all Xerox prints lived in the world of bitmap fonts. This is not really a language issue but an implementation fact at the time and made it in the end far superior despite everything else. (Plus the Mac used it and the LaserWriter was a huge success.)

- at the time Interpress handled multilingual fonts (as did Star) and that was added latter to PS but not when this was written. Interpress used XCCCS their 16bit character code standard which was the direct predecessor to Unicode (co developed initially by Xerox and Apple and I was part of that initial work.)

There are other key points but these are the major ones imho.


> Interpress could easily index the pages and just start printing from any where. Not so with PostScript.

Granted, a general purpose dot-ps file would have to be completely executed, yes, to get any particular page..

but no, not true after the early days.. Postscript structuring conventions allowed page extraction and therefor page execution after the header parts executed..


Exceptionally well written, and easy to follow. The impact of a textual encoding capable of being sent over almost any channel cannot be ignored. How well I recall the obsessional coding efficiency discussions of those days when bandwidth was so constrained. Now, we barely blink if an attachment in mail is 25MB but back then it could take 2 days to send that much data on a 1200baud link.

*Now we're dismayed by the 25MB limit.

I read this and it was one of those worthless CS papers that have a lot of verbiage but totally misses the point.

The meat is buried in the middle-end of the document:

"By now you can probably see the fundamental philosophical difference between PostScript and Interpress. Interpress takes the stance that the language system must guarantee certain useful properties, while PostScript takes the stance that the language system must provide the user with the means to achieve those properties if he wants them. With very few exceptions"

All the rest of it is sort of crap.

TL; DR: Postscript is a programming language that happens to be embedded in a printer and does printer things. Interpress is a PDL.


I was quite taken by the elision of the formation of Adobe - that particular gap informed quite a bit of my understanding of how PostScript’s choices came to be and led to a bit of rabbit hole brurrowing around the departures from Xerox.

Missed in the history in the article is that John Warnock and Chuck Geschke planned to build a computer/printer turnkey publishing system when they left Xerox. PS was just a piece of it. It was after a Steve Jobs meeting that changed their focus.

https://www.content-magazine.com/articles/adobe-founders/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: