🚀 go-pugleaf

In article <9447@imagen.UUCP> ib@apolling (Ivan N. Bach) writes:
>					If we leave it to Adobe to design our
>page and document description languages, by year 2000 we will still have to 
>waste our time preprocessing arithmetic expressions from the usual format
>supported by the first high-level procedural language into the Reverse
>Polish notation in order to make it easier to interpret such expressions.

Gee, I generally use programs to write most of the PostScript that I print.  I
don't see that this is a terrible problem. I don't usually write in
assembly code, except when I need to program to the metal; much the same as
my PostScript code.

>We will keep waiting for that readable data
>to be sent over a 9600-baud communications link to a printer controller
>that will take so long to process even these preprocessed statements that
>mechanical parts of a modern printer will wait on the electronic parts, so 
>that we will still not be able to drive our printers at full speed.

My DEC LPS-40 running real Adobe PostScript is ethernet attached.  I
don't know why people harp on the 9.6 kbs speed limit; if this is a
problem for you, it is easily solved by spending money for a high
performence printer.  Performance costs money.  And I like speaking TCP/IP 
to my PostScript printers so that its easily shared by multiple printing
platforms.  No one is holding a gun to your head forcing you to serially
attach your printers.

While PostScript is indeed a programming language, it intended purpose is
a <<Page Description Language>>, which it seems to do quite nicely.

Louis A. Mamakos