Masterminds of Programming: Chuck Moore (2009)(oreilly.com)

    Obvious Question:
      Why would anybody ever write a PostScript interpreter in PostScript?

    Possible Answers:
      To use as a debugging tool.
      To trace and single step through the execution of PostScript code.
      To serve as a basis for PostScript algorithm animation.
      To gain a deeper understanding of how PostScript works.
      To try out some ideas from Structure and Interpreteration.
      To experiment with extensions to the PostScript language.
      To demonstrate that PostScript isn't just for breakfast any more.
      To make PostScript run even slower (but thicker).
      To avoid programming in C (the portable assembly language of the 80's).
      To use to interpret its self.
      To have something nerdish to talk about at parties.
      [...]

    Date: Sun, 7 Jan 90 10:36:44 PST
    From: Russell Brand <[email protected]>
    To: [email protected]
    Subject: wuthel wisp klote

    >Somebody quoted you as saying something along the lines of "Lisp is
    >the language for people who want everything, and are willing to pay for
    >it." Is that how you put it?

    The quote is exactly right.  It is from a panel I led on the
    differences between Lisp, C, Ada, Pascal, Forth and Rex.

    From: [email protected] (Brent Callaghan)
    Newsgroups: comp.protocols.nfs
    Subject: NeFS Protocol Spec Available
    Keywords: NFS version 3
    Date: 13 Feb 90 01:57:31 GMT

    NeFS is not NFS.  It started out as an NFS protocol rev
    (NFS version 3) but its protocol is a radical departure
    from the NFS's remote procedure call model.  In order
    to avoid confusion with NFS we're calling it NeFS for
    now - Network Extensible File System (the similarity of
    the name to a window system protocol is entirely intentional).