https://pbfcomics.com/comics/beach-closing/
> Using a Turing complete language for drawing was scary.
Not particularly sure why. Aren't all apps using Turing complete languages to draw on screen? It's just a question of which layer that happens.
Display PostScript did the same, surely?
More flexible still is producing commands that can contain loops like Postscript. Now we're in tricky territory, because it's easy to make a mistake that e.g. produces an infinite loop and the whole display locks up. And it's much harder to reason about such things as the update rate of the drawing process because the drawing commands are themselves Turing complete.
This doesn't matter when you're merely printing because there is no refresh. Not so with an interactive display. That's why the "Display" in "Display Postscript" was a big deal.
With PostScript, you can have a document that renders differently every time you open it (on purpose). Or a file that will never finish rendering or printing, like the infinite loop you mentioned.
PostScript infinite possibilities are cool and cute, but not all that practical for a graphics description language.
There was a font, wasn't there -- was it Just van Rossum's Beowulf -- that drew itself slightly differently every time? Can't find a reference now.
edit: it was!
> BeOS was a very different operating system and -- let's be clear -- would have been a terrible, terrible choice.
Oh, sure. But it sure was snappy. And gorgeous. And that file system was awesome.