The Jargon File Turns 50: Terms That Didn't Survive

The Jargon File has been documenting hacker culture since 1975. Not every term made it. Here are the linguistic casualties — and what their extinction tells us about how tech culture evolves.

A Dictionary for a Subculture

When Raphael Finkel began compiling the Jargon File at Stanford in 1975, he was documenting the living language of a small, tight-knit community. Updated by Guy Steele, then maintained by Eric S. Raymond (who published it as "The New Hacker's Dictionary" in 1991), the Jargon File captured terms that were vibrant, specific, and often hilarious. But language is a living thing, and not all of its specimens survive.

The Jargon File was not the first attempt to document hacker slang. The TMRC Dictionary, compiled by members of MIT's Tech Model Railroad Club in the late 1950s and early 1960s, predates it by over a decade. But the Jargon File was the first to circulate widely through the ARPANET, reaching hacker communities at universities and research labs across the country. Its distribution mechanism was as important as its content: a living document, passed between systems, updated by contributors, growing organically. It was, in a sense, a proto-wiki.

The early Jargon File reflected the world of its creators: MIT, Stanford, and Carnegie Mellon hackers working on PDP-10s, running ITS (Incompatible Timesharing System) or TOPS-20, programming in LISP and assembler. The terms were shaped by the hardware they used, the culture they shared, and the humor that sustained them through all-night programming sessions. Many entries were inside jokes that required deep context to understand. That was part of the point. The Jargon File was not written for outsiders. It was a mirror that the community held up to itself.

Some terms died because their referents vanished. "Core dump" persists metaphorically, but who remembers "core" as magnetic core memory? "Strstrstrstrstr" (the sound of a card reader) died with punch cards. "BLT" (Block Transfer) survives only in sandwich form. These are linguistic fossils — imprints of technologies that shaped thinking but no longer exist.

The Three Editors

The Jargon File's character was shaped by its three primary editors, each of whom left a distinct imprint.

Raphael Finkel, who started the file in 1975 at Stanford, was a compiler researcher. His contributions were technical and precise, focused on programming concepts and system administration terminology. The initial collection was small, perhaps a few hundred entries, and it reflected the vocabulary of a single lab.

Guy Steele took over in the late 1970s. Steele, who would go on to co-design Scheme and write the Java Language Specification, brought a linguist's sensibility. He formalized the file's structure, added pronunciation guides and usage notes, and expanded the collection to include terms from multiple hacker communities. The Steele era established the Jargon File as a legitimate reference work, not just a list of slang.

Eric S. Raymond (ESR) became the maintainer in 1990 and published the file as "The New Hacker's Dictionary" through MIT Press in 1991 (with a second edition in 1993 and a third in 1996). Raymond's stewardship was the most controversial. He expanded the file significantly, adding terms from Usenet and the broader internet culture. Critics accused him of injecting his own political views and of adding entries that reflected his personal vocabulary rather than community consensus. The Raymond era is also when the Jargon File became widely known outside the hacker community, which was both its greatest achievement and, for purists, its greatest betrayal.

The Beautiful Dead

"Gronk" (to break or damage) was standard hacker vocabulary in the 1970s. "Winnage" and "lossage" (states of winning or losing) were common enough to appear in everyday conversation at MIT and Stanford. "Strstrstr" was the sound of a line printer. "Cuspy" meant "unusually good" — a term so precisely useful that its extinction feels like a loss to the English language.

"DWIM" — Do What I Mean — was both a concept and a critique. It described a system smart enough to interpret user intent despite imprecise commands, and it was also a joke about the impossibility of such systems. In the age of LLMs, DWIM has arguably been achieved, but the term itself is forgotten by the people building the systems that embody it.

"Langrick" described a particularly inelegant solution. "Cretinous" was a common adjective for poorly designed systems. "Strstrstr," beyond being onomatopoeia for a line printer, was also used metaphorically to describe any tedious, repetitive process. "Bibble" meant to eat or drink while hacking. "Crufty" described software that was poorly built, overly complex, or in a state of decay. (This one has partially survived, but mostly in the mouths of programmers who read the Jargon File as students.)

Some of the most colorful dead terms were compound constructions. "Strstrstr" and "BLT" have already been mentioned, but consider also "feeping creaturism" (the tendency of software to accumulate unnecessary features, a playful corruption of "creeping featurism"), "bogosity" (the degree to which something is bogus), and "langrick" (a hack that is technically functional but aesthetically offensive). Each of these filled a precise lexical niche, and the English language is slightly poorer for their absence.

The Survivors

The terms that survived — "hack," "bug," "daemon," "foo/bar," "grok" — share common traits: they're short, they fill lexical gaps (no other word means quite the same thing), and they crossed the boundary from subculture to mainstream. The terms that died were often longer, more context-dependent, or too tied to specific hardware.

"Grok," borrowed from Robert Heinlein's "Stranger in a Strange Land" (1961), means to understand something so thoroughly that it becomes part of you. No English word captures this depth of understanding. "I understand it" is not the same as "I grok it." The former is intellectual. The latter is visceral. The word survived because it fills a gap that no other word fills.

"Foo" and "bar" (and their companion "baz") are metasyntactic variables, placeholder names used in examples and documentation. Their origin is debated (possibly from the WWII slang "FUBAR," or possibly from an MIT tradition), but their function is clear: when you need a name that means nothing, you use "foo." The terms survived because programmers need placeholder names constantly, and these have become the universal convention.

"Bug" predates computing (Thomas Edison used it in 1878), but its modern meaning was cemented when Grace Hopper's team found an actual moth in a relay of the Harvard Mark II in 1947 and taped it into the logbook with the annotation "First actual case of bug being found." The term survived because software defects need a name, and "bug" is short, vivid, and slightly humorous.

"Daemon," discussed elsewhere in this collection, survived because the concept it describes (a background process) is fundamental to computing. The word is technically precise, euphonically distinctive, and culturally rich. It had everything a surviving word needs.

What the Jargon File Reveals About Culture Change

The Jargon File also reveals how hacker culture's values have shifted. Early entries celebrate cleverness, elegance, and playful subversion. Later additions reflect the commercialization of tech: "vaporware," "bloatware," "golden handcuffs." The vocabulary of a counterculture became the vocabulary of an industry. Some would call that growth. Others would call it gentrification.

The early Jargon File entries assume a shared context that no longer exists. They reference specific machines (the PDP-10, the PDP-11, the Lisp Machine), specific operating systems (ITS, TOPS-20, Multics), and specific physical spaces (the MIT AI Lab, the Stanford AI Lab, Xerox PARC). The community was small enough that everyone knew everyone, and the language reflected that intimacy. Terms could be allusive, ironic, and multi-layered because the audience shared enough context to decode them.

As computing expanded from a research pursuit to a mass industry, the language simplified. New terms were more descriptive, less allusive. "Refactoring" is a precise technical term with no humor. "Microservices" describes exactly what it means. "Container" is a metaphor, but a transparent one. The linguistic playfulness that characterized the original hacker vocabulary has largely been replaced by clarity and accessibility. This is probably necessary for an industry that employs millions of people, but something has been lost.

The Jargon File also documents the geographic fragmentation of hacker culture. MIT and Stanford had different vocabularies. CMU had its own terms. When these communities connected through the ARPANET, their vocabularies merged, competed, and sometimes split. The process was similar to dialect formation in natural languages: isolated communities develop distinctive vocabularies, and contact between communities leads to convergence.

The Jargon File's Legacy in Modern Tech

Modern tech culture continues to produce new jargon, though the process has changed. Terms now spread through Twitter, Hacker News, blog posts, and conference talks rather than through ARPANET mailing lists. The velocity of spread is orders of magnitude faster, but the staying power may be lower. "10x engineer," "thought leader," "disrupt," and "pivot" are terms that emerged in the 2010s and may not survive the 2030s.

Some modern terms follow the Jargon File's tradition of playful precision. "Yak shaving" (performing a series of tasks, each of which seems necessary before the previous one can be completed, but which are increasingly tangential to the original goal) is a perfect example. The term, which comes from a "Ren and Stimpy" episode, fills a lexical gap that the original Jargon File authors would have appreciated. "Rubber duck debugging" (explaining your code to an inanimate object to find bugs) is another modern term that carries the spirit of the original Jargon File: precise, humorous, and grounded in real practice.

What Survival Tells Us

What's clear is that the Jargon File remains an invaluable archaeological record — a snapshot of a community's DNA at various stages of its evolution. The terms that died aren't failures; they're data points in the story of how a subculture became the dominant culture of the 21st century.

The file also serves as a reminder that technical communities are linguistic communities. The words we use shape how we think about problems. "Refactoring" is not just a word for restructuring code. It is a word that implies the code's behavior should not change, only its structure. "Technical debt" is not just a word for messy code. It is a metaphor that implies the mess accrues interest and must eventually be repaid. The Jargon File's greatest contribution was not any individual term but the demonstration that hacker vocabulary was rich enough, precise enough, and culturally significant enough to deserve documentation.

Fifty years after Raphael Finkel started collecting words at Stanford, the Jargon File endures as the founding document of a linguistic tradition. The specific terms may come and go, but the impulse to name things precisely, humorously, and with attention to intellectual lineage remains at the heart of computing culture.

The Pronunciation Problem

One of the Jargon File's most distinctive features was its pronunciation guides. Hacker jargon was primarily a written language, spread through email, Usenet, and source code comments. When hackers met in person, they often discovered that they had been pronouncing the same words differently for years. The Jargon File attempted to resolve these disputes, but it also documented them.

"/dev/null" was straightforward enough, but what about "char" (as in character type)? Is it "care" or "char" (rhyming with "car")? The Jargon File noted both pronunciations and declared neither authoritative. "SQL" could be "sequel" or "ess-cue-ell," a debate that continues to this day. "GIF" (Graphics Interchange Format) was declared as having a soft 'g' by its creator Steve Wilhite, but the Jargon File documented the ongoing holy war without taking sides.

Some pronunciation disputes were more obscure. "Bstrstrstr" (used to represent incomprehensible technical jargon) was, by definition, unpronounceable. "#!" (the shebang at the beginning of Unix scripts) was variously pronounced "hash-bang," "sharp-bang," "pound-bang," or "she-bang" depending on which community you belonged to.

The pronunciation entries revealed something important about hacker culture: it was primarily textual. Hackers communicated through terminals, email, and code, not through speech. This meant that the vocabulary could evolve for decades without anyone agreeing on how the words sounded. The written word was primary; the spoken word was a best-effort approximation.

The Political Dimension

The Jargon File was never apolitical, but its political leanings shifted over time. The early editions reflected the libertarian, anti-authoritarian stance of the MIT and Stanford AI labs. Terms like "suit" (a business person) and "marketroid" (someone from marketing) carried clear disdain for corporate culture. "Strstrstr" (bureaucratic process) was defined with obvious contempt. The early hackers saw themselves as a meritocratic elite whose values were incompatible with corporate hierarchy.

Under Raymond's editorship, the file acquired a more explicitly libertarian and free-market orientation. Raymond's own political views (he is an advocate for gun rights and libertarian economics) influenced his editorial choices, a fact that critics were quick to note. Some entries seemed more like Raymond's personal opinions than community consensus. The tension between "documenting the culture" and "shaping the culture" was never fully resolved.

The Free Software Foundation's Richard Stallman, who had been part of the original MIT hacker culture, accused Raymond of co-opting the Jargon File to advance an agenda that was not representative of the broader community. The disagreement mirrored the larger split between Stallman's "free software" movement (which emphasized ethical principles) and Raymond's "open source" movement (which emphasized practical benefits). The Jargon File became a minor front in a major culture war.

Digital Archaeology and Preservation

The Jargon File exists today in a curious state. Raymond's website hosts the latest version, but updates have been infrequent since the early 2000s. The file has effectively been frozen, a snapshot of hacker culture as it existed at the turn of the millennium. New terms ("blockchain," "container," "microservice," "DevOps") are absent. The Jargon File has become a historical document rather than a living dictionary.

Several efforts have attempted to create successors. The Urban Dictionary, while not hacker-specific, serves a similar function of crowdsourced slang documentation. Wikipedia's computing jargon articles provide more formal documentation. Stack Overflow's tag wikis capture the working vocabulary of modern developers. But none of these captures the specific combination of precision, humor, and cultural specificity that made the Jargon File unique.

The Internet Archive's preservation of the Jargon File's various versions provides a fascinating timeline of linguistic change. Comparing the 1983 edition (primarily PDP-10 and LISP vocabulary) with the 1996 edition (which includes internet and PC terminology) reveals the speed at which the hacker community's vocabulary adapted to new technology. The additions tell you what was new and exciting. The deletions tell you what had become irrelevant or mainstream enough that it no longer needed special documentation.

Key Takeaways