Gutenberg Articles

Appearance

Excerpt ​

Excerpt from The Jargon File, Version 2.9.10, 01 Jul 1992, by Unknown Author

🐉 n. [MIT] A program similar to a {daemon}, except that
it is not invoked at all, but is instead used by the system to
perform various secondary tasks. A typical example would be an
accounting program, which keeps track of who is logged in,
accumulates load-average statistics, etc. Under ITS, many
terminals displayed a list of people logged in, where they were,
what they were running, etc., along with some random picture (such
as a unicorn, Snoopy, or the Enterprise), which was generated by
the name dragon'. Usage: rare outside MIT --- under UNIX and most<br /> other OSes this would be called a background demon' or
{daemon}. The best-known UNIX example of a dragon is
cron(1)'. At SAIL, they called this sort of thing a<br /> phantom'.

:Dragon Book: n. The classic text Compilers: Principles,<br /> Techniques and Tools', by Alfred V. Aho, Ravi Sethi, and Jeffrey D.<br /> Ullman (Addison-Wesley 1986; ISBN 0-201-10088-6), so called because<br /> of the cover design featuring a dragon labeled complexity of
compiler design' and a knight bearing the lance LALR parser<br /> generator' among his other trappings. This one is more<br /> specifically known as the Red Dragon Book' (1986); an earlier
edition, sans Sethi and titled Principles Of Compiler Design'<br /> (Alfred V. Aho and Jeffrey D. Ullman; Addison-Wesley, 1977; ISBN<br /> 0-201-00022-9), was the Green Dragon Book' (1977). (Also New<br /> Dragon Book', Old Dragon Book'.) The horsed knight and the
Green Dragon were warily eying each other at a distance; now the
knight is typing (wearing gauntlets!) at a terminal showing a
video-game representation of the Red Dragon's head while the rest
of the beast extends back in normal space. See also {{book
titles}}.

:drain: [IBM] v. Syn. for {flush} (sense 2). Has a connotation
of finality about it; one speaks of draining a device before taking
it offline.

Explanation ​

This excerpt is from The Jargon File (also known as The New Hacker’s Dictionary), a compilation of slang, technical terms, and cultural references from the early computing and hacker communities, particularly those associated with MIT, Stanford (SAIL), and Unix systems. The text reflects the playful, insider language of programmers and system architects from the 1970s–1990s, blending technical precision with humor and metaphor. Below is a detailed breakdown of the excerpt, focusing on the text itself while incorporating context, themes, and literary devices where relevant.

1. :dragon: n. ​

Literal Meaning and Technical Context ​

  • A dragon is defined as a type of system program that runs autonomously (like a daemon), but unlike a daemon, it is not explicitly invoked by users or other programs. Instead, it performs secondary tasks in the background, such as:
    • Accounting (tracking logins, system usage).
    • Generating dynamic displays (e.g., the "name dragon" on MIT’s ITS system, which showed logged-in users alongside random images like unicorns or the Enterprise).
  • The term is rare outside MIT, where similar programs might be called daemons (Unix) or phantoms (SAIL).
  • Example: cron(1) (a Unix utility for scheduling tasks) is cited as a "dragon" because it runs periodically without direct user interaction.

Themes and Cultural Significance ​

  • Metaphor and Playfulness: The term dragon evokes a mythical, autonomous creature—fitting for a program that operates invisibly but powerfully. This reflects the hacker culture’s love of whimsical metaphors (e.g., daemons, goblins) to describe abstract technical concepts.
  • Institutional Jargon: The entry highlights how terminology varies across institutions (MIT vs. SAIL vs. Unix). This underscores the fragmented, tribal nature of early computing cultures, where each group developed its own slang.
  • Nostalgia for ITS: The reference to ITS (MIT’s Incompatible Timesharing System) and its "name dragon" reflects a lost era of computing where systems were highly customized and visually playful (e.g., terminals displaying ASCII art). Modern systems prioritize efficiency over such flourishes.

Literary Devices ​

  • Analogy: Comparing background processes to dragons (or daemons/phantoms) makes abstract concepts tangible.
  • Juxtaposition: The contrast between MIT’s dragon, Unix’s daemon, and SAIL’s phantom emphasizes the diversity of technical cultures.
  • Humorous Undercutting: The parenthetical "(such as a unicorn, Snoopy, or the Enterprise)" injects levity, reinforcing the hacker ethos of not taking oneself too seriously.

2. :Dragon Book: n. ​

Literal Meaning and Technical Context ​

  • Refers to Compilers: Principles, Techniques, and Tools (1986) by Aho, Sethi, and Ullman, a seminal textbook on compiler design.
  • The nickname comes from its cover art: a knight (representing the compiler writer) facing a dragon labeled "complexity of compiler design", armed with tools like an LALR parser generator (a type of parsing algorithm).
  • Editions:
    • Red Dragon Book (1986): The second edition, with Sethi as co-author.
    • Green Dragon Book (1977): The first edition (Principles of Compiler Design), without Sethi.
  • The visual metaphor evolves between editions:
    • Green Dragon: Knight and dragon eye each other from a distance (symbolizing the challenge of compiler design).
    • Red Dragon: The knight is now typing at a terminal, with the dragon’s head appearing on-screen (reflecting the shift to interactive computing).

Themes and Cultural Significance ​

  • Rite of Passage: The Dragon Book is a canonical text for computer science students, akin to a "bible" for compiler theory. Its nickname reflects its intimidating reputation—mastering it is a milestone.
  • Evolution of Technology: The change in cover art mirrors the transition from theoretical (1977) to practical (1986) compiler design, as tools like parser generators became more accessible.
  • Hacker Humor: The knight’s gauntlets (worn while typing) and the dragon’s digital manifestation are absurd yet apt, blending medieval imagery with modern computing.

Literary Devices ​

  • Symbolism: The dragon represents the complexity of compiler design, while the knight’s tools (e.g., LALR parser generator) symbolize the weapons used to tame it.
  • Visual Storytelling: The cover art tells a mini-narrative of progress—from cautious standoff to active engagement—mirroring the field’s maturation.
  • Allusion: The "Dragon Book" name alludes to mythic quests, framing compiler design as an epic battle against chaos.

3. :drain: v. ​

Literal Meaning and Technical Context ​

  • A synonym for flush (sense 2), meaning to clear or empty a device’s buffers or queues before taking it offline.
  • Connotation: Implies finality—e.g., "draining a device" suggests a deliberate, thorough purge, often as a precursor to maintenance or shutdown.
  • IBM Origin: The term likely comes from IBM’s mainframe culture, where precise, ritualistic procedures were critical (e.g., ensuring no data was lost when deactivating hardware).

Themes and Cultural Significance ​

  • Ritual and Precision: The term reflects the methodical, almost ceremonial nature of early system administration, where actions like "draining" were part of a checklist to avoid disasters.
  • Contrast with Modern Usage: Today, terms like flush or sync are more common, but drain carries a weightiness that hints at the high stakes of early computing (e.g., mainframes handling critical data).
  • Institutional Language: Like dragon vs. daemon, drain is IBM-specific jargon, reinforcing how corporate and academic cultures shaped technical vocabulary.

Literary Devices ​

  • Metaphor: "Draining" evokes plumbing—a physical analogy for data flow, common in computing (e.g., pipes, streams).
  • Connotation vs. Denotation: While flush is neutral, drain suggests exhaustion or completion, adding emotional weight to a technical act.

Overarching Themes in the Excerpt ​

  1. Language as Culture: The entries show how technical jargon is not just functional but cultural, reflecting the values, humor, and history of specific communities (MIT’s playfulness, IBM’s formality).
  2. Metaphor and Myth: Computing terms often borrow from mythology (dragons, daemons) or everyday life (draining), making abstract concepts memorable.
  3. Evolution of Technology: The Dragon Book’s cover art and the rarity of dragons outside MIT highlight how terminology and practices change as systems evolve.
  4. Insider vs. Outsider Knowledge: The text assumes familiarity with concepts like daemons or ITS, creating a sense of exclusivity—a hallmark of hacker/jargon dictionaries.

Significance of The Jargon File ​

  • Historical Record: It preserves the folklore of early computing, offering insights into how programmers thought and communicated.
  • Bridge Between Generations: Terms like dragon or Dragon Book persist in modern tech culture (e.g., "slaying the dragon" for solving a hard problem), linking past and present.
  • Humor and Humanity: The playful tone reminds us that even in highly technical fields, language is creative and human.

Final Thoughts ​

This excerpt is a microcosm of The Jargon File’s charm: it’s technically precise yet richly metaphorical, historically grounded yet whimsical. The definitions do more than explain terms—they tell stories about the people, institutions, and machines that shaped computing. Whether it’s a dragon lurking in MIT’s systems or a knight battling compiler complexity, the text reveals how language turns code into culture.

Questions ​

Question 1 ​

The passage’s treatment of the term dragon (as distinct from daemon or phantom) primarily serves to:

A. underscore the technical superiority of MIT’s ITS system over Unix by highlighting its unique terminology.
B. illustrate how early computing cultures used mythological metaphors to mask the mundanity of system processes.
C. reveal the fragmented, institution-specific nature of technical jargon as a reflection of discrete hacker subcultures.
D. argue that MIT’s terminology was more precise than Unix’s, given the functional differences between dragons and daemons.
E. critique the arbitrary proliferation of synonyms in computing, where dragon, daemon, and phantom describe identical processes.

Question 2 ​

The shift in the Dragon Book’s cover art between the 1977 and 1986 editions most strongly suggests that the authors intended to:

A. mirror the transition from theoretical compiler design to practical, interactive implementation.
B. appeal to a broader audience by replacing abstract symbolism with a more literal depiction of programming.
C. emphasize the increasing complexity of compiler design by making the dragon appear more technologically integrated.
D. distance the second edition from the first by adopting a more modern, less medieval aesthetic.
E. subtly critique the over-reliance on LALR parsers by depicting the knight as overly dependent on tools.

Question 3 ​

The parenthetical list in the dragon entry—“such as a unicorn, Snoopy, or the Enterprise”—functions primarily to:

A. undermine the gravity of the technical explanation with a sudden intrusion of whimsy, reinforcing hacker culture’s irreverence.
B. provide concrete examples of how the “name dragon” personalized user interfaces, thereby improving system usability.
C. highlight the cultural diversity of MIT’s user base by referencing both highbrow (unicorn) and pop-culture (Snoopy) icons.
D. contrast the seriousness of system accounting with the frivolity of ASCII art, exposing a tension in early computing priorities.
E. demonstrate the arbitrary nature of the “name dragon”’s image selection, which had no functional correlation to system tasks.

Question 4 ​

The term drain, as defined in the passage, acquires its connotation of “finality” most directly from its:

A. etymological roots in plumbing metaphors, where “draining” implies an irreversible emptying.
B. association with IBM mainframes, where procedures were rigidly formalized to prevent data loss.
C. contrast with the more temporary implications of flush, which lacks the same procedural weight.
D. use as a precursor to taking a device offline, a high-stakes action in early computing environments.
E. syntactic parallel to commands like kill or terminate, which also denote decisive, non-reversible operations.

Question 5 ​

Which of the following best describes the passage’s overarching perspective on the relationship between technical jargon and computing culture?

A. Jargon emerges as a necessary shorthand to compensate for the inherent complexity of computing systems.
B. The playfulness of terms like dragon reflects a deliberate effort to make intimidating concepts more accessible.
C. Institution-specific slang is a relic of early computing, destined to fade as systems become more standardized.
D. Metaphors in technical language serve primarily to obfuscate, creating barriers between insiders and outsiders.
E. Technical terminology is not merely functional but cultural, encoding the values, humor, and history of its users.

Solutions and Explanations ​

1) Correct answer: C ​

Why C is most correct: The passage emphasizes that dragon is a term “rare outside MIT” and contrasts it with Unix’s daemon and SAIL’s phantom. This juxtaposition highlights how different institutions developed their own jargon for functionally similar concepts, reflecting discrete subcultures within early computing. The focus is on the fragmented, localized nature of technical language, not on technical superiority (A), metaphorical masking (B), precision (D), or arbitrary synonymy (E).

Why the distractors are less supported:

  • A: The passage does not claim MIT’s terminology is superior; it merely notes its uniqueness. The tone is descriptive, not evaluative.
  • B: While mythological metaphors are present, the primary purpose of the distinction is not to “mask mundanity” but to illustrate institutional variation.
  • D: There is no argument that MIT’s term is more precise; the entry treats the terms as functionally equivalent but culturally distinct.
  • E: The passage does not critique the proliferation of synonyms; it presents the variation as a neutral fact of hacker culture.

2) Correct answer: A ​

Why A is most correct: The 1977 Green Dragon cover shows the knight and dragon at a distance (theoretical standoff), while the 1986 Red Dragon cover depicts the knight actively typing at a terminal with the dragon’s head on-screen (practical engagement). This shift mirrors the evolution from abstract compiler theory to hands-on implementation, where tools like parser generators became central to real-world use.

Why the distractors are less supported:

  • B: The change is not about broadening appeal but about reflecting a technological shift in the field.
  • C: While the 1986 dragon is more “integrated,” the focus is on the knight’s interactive role, not the dragon’s complexity.
  • D: The medieval aesthetic persists (knight, dragon); the change is in the activity depicted, not a rejection of the theme.
  • E: There is no critique of LALR parsers; the lance is presented as a tool, not a crutch.

3) Correct answer: A ​

Why A is most correct: The parenthetical list—“unicorn, Snoopy, or the Enterprise”—is tonally jarring amid a technical definition. Its abrupt whimsy undercuts the seriousness of the explanation, embodying hacker culture’s irreverence and resistance to taking itself too seriously. This aligns with the passage’s broader theme of playful subversion in technical language.

Why the distractors are less supported:

  • B: The list does not explain how the images improved usability; it’s a stylistic flourish, not a functional description.
  • C: The examples are not systematically “highbrow” or “pop-culture”; they’re random and eclectic, chosen for humor, not cultural analysis.
  • D: There is no tension exposed; the passage celebrates the frivolity as part of the culture, not as a critique.
  • E: The images do correlate with system tasks (displaying logged-in users); the parenthetical highlights their arbitrary charm, not their irrelevance.

4) Correct answer: E ​

Why E is most correct: The “finality” of drain stems from its syntactic and semantic parallel to commands like kill or terminate—all of which denote decisive, non-reversible actions in computing. The passage notes that drain is used before taking a device offline, a context where permanence is implied (e.g., ensuring no data remains). This aligns with the weighty connotations of irreversible operations.

Why the distractors are less supported:

  • A: While plumbing metaphors are relevant, the passage does not emphasize irreversibility in the metaphor itself—it’s the computing context that adds finality.
  • B: IBM’s formality is mentioned, but the connotation arises from the command’s function, not institutional culture.
  • C: Flush can also imply finality (e.g., flushing a buffer before shutdown); the distinction is not about temporariness but about drain’s stronger association with pre-offline procedures.
  • D: The high stakes of early computing contribute, but the connotation is linguistic (parallel to kill/terminate), not solely contextual.

5) Correct answer: E ​

Why E is most correct: The passage repeatedly shows that technical terms (e.g., dragon, Dragon Book, drain) are not just functional labels but cultural artifacts. They encode:

  • Values (e.g., playfulness in dragon’s random images).
  • Humor (e.g., the absurdity of a knight typing in gauntlets).
  • History (e.g., the evolution of the Dragon Book’s cover art). This aligns with the overarching theme that jargon is a cultural practice, not merely a utilitarian tool.

Why the distractors are less supported:

  • A: Jargon’s function as shorthand is acknowledged, but the passage emphasizes its cultural richness, not just efficiency.
  • B: Playfulness is present, but the primary focus is on how terms reflect culture, not just simplify concepts.
  • C: The passage does not suggest slang is “destined to fade”; it treats it as a persistent, meaningful aspect of computing history.
  • D: Metaphors are not framed as obfuscatory but as expressive and unifying within subcultures.