Chatbots Decoded: Exploring AI is a new exhibit from the Computer History Museum (CHM) opening November 20th, 2024. In development for more than a year, the exhibit covers both the history of chatbots and conversational interfaces as well as the social ramifications of the technology. While there is not an explanation for why GPUs rather than CPUs are so useful for learning or what “attention is all you need” means, both are alluded too and I think, many audiences, including children, will enjoy it.
Many corporations and agencies allocate a certain amount of their budget towards the creation of public artwork. For instance, New York’s Metropolitan Transportation Authority (MTA) has funded nearly 300 permanent art installations since 1982 under the city’s “Percent for Art” law. If we question the effectiveness of the program, we immediately run into problems of measuring the subjective aesthetic value of the creations.
In December 2022, Adobe, through the Computer History Museum (CHM), released the source code for PostScript®, version 1.0. PostScript is one of the foundational technologies of the desktop publishing revolution of the early 1980s, along with laser printers, the graphical user interface of the Apple Macintosh, and Aldus PageMaker. PostScript is a programming language and a page description format for translating visual content into printed documents.
Adobe immediately enjoyed business success through licensing PostScript to laser printer manufacturers and it became the de facto digital publishing format. While multiple histories have studied this event through a business lens, what historical questions may be answered through the source code? Further, as software practitioners, what can we learn from the source code to apply to present and future designs?
We argue:
PostScript’s design and implementation benefited from a long lineage of other software programs (as Adobe has always admitted),
The software architecture aligned with the interests of creatives, printer services, and printer manufacturers,
Design choices, including modularity and semantics, added value to the product, and
Pursuing the “print anything” objective, rather than page printing throughput, yielded a superior implementation.