Why do you say that? It's a very simple and tiny language that you can learn in an afternoon. Far from the utter complexity of modern things. It's barely more complicated than a programmable calculator. Certainly simpler, cleaner, and arguably more powerful than svg graphics.
You don't even need to read any manual to guess what this example program does:
Although it would, at times, go wrong there are very few things to this day that do impress me more than typing this (admire my "useless use of cat" btw):
... $ cat tiger.ps | netcat 192.168.0.78 9100
And see my HP LaserJet 4M+ (speaking PostScript natively) start printing.
Yeah, yeah, yeah, I do have a SOHO and a modern printer/scanner at home and it can do more stuff.
But the elegance of netcat'ing a PostScript file to a printer and seeing it print without needing any driver nor any configuration whatsoever [1] was quite something.
It was simpler indeed and it was elegant and it did feel like magic.
Now it wasn't fun if you printed many pages and suddenly it started printing garbage but still...
[1] you had to configure the printer itself to get an IP, but that was done on the printer itself
PostScript's magic is subtle. I once tried writing a PostScript interpreter in ADA. Got far enough to display the turkey example and realized that PostScript code can modify itself and decided I didn't want to go there.
I've done a bit of PostScript programming in the dim and distant past - the most ambitious of which was a "pretty-printer" for the YAM email client on Amiga, which otherwise just printed emails as plain ASCII.
I found PostScript to be one of those things where something "clicks" after a while, and I really started to appreciate the elegance and simplicity. The hardest part is the mental gymnastics required to track what's on the stack and in what order!
It's not a terrible language; it just requires a little different thinking. In 1988/89, I learned to write a postscript generator with no dev environment, just reams of paper. Debugging was hard since you had to add debugging print statements in the same document you were printing, which was hard if no printing occurred! I read Adobe Illustrator files, which were the precursor to PDF, so at least I had something to look at.
Why do you say that? It's a very simple and tiny language that you can learn in an afternoon. Far from the utter complexity of modern things. It's barely more complicated than a programmable calculator. Certainly simpler, cleaner, and arguably more powerful than svg graphics.
You don't even need to read any manual to guess what this example program does: