Coming from a functional background, the point-free nature of it wasn't too confusing, and I actually grew to really enjoy it.
I never got too far into that quest largely because I didn't have much of a practical need to be a Postscript expert, but it has since made me want to learn Forth, which I have been pushing off for months now.
I wanted to draw an fairly detailed energy-level diagram for a particular atom and I wanted the it done to scale -- except for certain fudges made for clarity.
The amount of repetitive calculation and not-quite-trivial logic meant it made sense to use a a programming language rather than a "simple" document format. I chose hand-written PostScript mostly for fun.
But PS actually quite a nice language for the task -- no worse than the various Python libraries which would have been my main alternative.
In case you're interested in having another reason, Bill Casselman does marvellous things with Postscript; e.g., http://www.math.ubc.ca/~cass/graphics/manual .
1) back when I had a database (Foxbase, not FoxPro, Foxbase), Turbo C, and a PostScript printer, but no reporting tool and a requirement to generate some graphs.
It was quite fun but I still can't say that I know much about actually using Forth :)
You can't just write that. Chuck Moore, I assert with no evidence whatsoever, would require that you write "so I went forth and implemented …."
Fortunately, the next step, which will teach you the language, is even more fun: Bootstrap your interpreter.
I figured that web servers tend to be pretty fun to write and if someone else has figured out how to do one in PS, I would be clever enough to build one too.
I guess I was wrong about that because I didn't get very far.