PostScript is a high-level programming language.

The fact that it is a computer language means that it has its own vocabulary and grammar that are used to create a list of instructions that tell a computer system what to do. As with all computer languages, the slightest deviation from the well defined conventions of the language results in an error message and a computer system that refuses to do anything at all. If you print a job to a PostScript device and a network glitch causes the ’showpage’ command to arrive as “shopage” at the output device, the system will happily generate an ‘undefined’ error message and refuse to print your job, even though it has already processed your entire page and the ’showpage’ command is simply there to tell the output device that it can start outputting your masterpiece.

PostScript is a high-end programming language, which means that even mere humans can still look at the instructions and understand what they mean. If you open a PostScript program with a word processor or editor, it may look like this:

%%BeginProlog %%BeginResource: procset AdobePS_Win_Feature_Safe 4.2 0 userdict begin/lucas 21690 def /featurebegin{countdictstack lucas[}bind def /featurecleanup {stopped {cleartomark dup lucas eq{pop exit}if}loop countdictstack exch sub dup 0 gt{{end}repeat}{pop}ifelse}bind def end %%EndResource

It can take a while to understand what the above gibberish means, but you can learn to make sense of it. Of course, this will take years and by the time you are that proficient in programming, your youth will have passed, your computer screen will be more important to you than anything else in the world and the opposite sex will remain a complete mystery to you for the rest of your life (although I am willing to admit that I don’t know how to program and can’t make much sense of women either.)