[smurpy]

Hey, that's a pretty handy document. Interesting to see it support PS in the context of LaTeX and Word.

I used to dream in PostScript I was coding in it so much -- the experience was dreaming about stack-oriented coding, as opposed to vector visuals, for clarity. I got started coding in PS on the NeXT in '91 doing data driven graph visualizations. PS was great for some algorithmically-generated logos too. Really fun were some fractals which strained the imagesetters and printers they ran on. Learning PS really paid off though when I ended up using it to create a database publishing engine for real-estate listings. It used Python for data wrangling and orchestration and then PostScript for the dynamic book generation and layout. It was used back when real estate agents relied on giant books printed daily, which this engine generated for dozens of markets across Western Canada. These documents were pretty gnarly too, including property-type-specific templates, various indexes, property images, market-specific variations, etc -- and doing all that with the absolute control which PostScript permitted was fantastic. It would have been nightmarish to try to do such things in LaTeX, Word or the DTP tools of the era. PDF rendering was automated with GhostView so the whole toolchain was open source.

I'd suggest that if extreme precision, detail and complexity are your requirements and especially if rendering to PDF and screen bitmaps are needed then PostScript is still very relevant. It's also quite fun as a developer.