Surveys have shown the Allman and Whitesmiths styles to be the most
common, with about equal mind shares. K&R/1TBS used to be nearly
universal, but is now much less common in C (the opening brace tends
to get lost against the right paren of the guard part in an if or
while, which is a Bad Thing). Defenders of 1TBS argue that any
putative gain in readability is less important than their style's
relative economy with vertical space, which enables one to see more
code on one's screen at once.
The Java Language Specification legislates not only the capitalization
of identifiers, but where nouns, adjectives, and verbs should be in
method, class, interface, and variable names (section 6.8). While the
specification stops short of also standardizing on a bracing style,
all source code originating from Sun Laboratories uses the K&R style.
This has set a precedent for Java programmers, which most follow.
Doubtless these issues will continue to be the subject of holy
Node:index of X, Next:infant mortality, Previous:indent
style, Up:= I =
index of X n.
See coefficient of X.
Node:infant mortality, Next:infinite, Previous:index of X,
Up:= I =
infant mortality n.
It is common lore among hackers (and in the electronics industry at
large; this term is possibly techspeak by now) that the chances of
sudden hardware failure drop off exponentially with a machine's time
since first use (that is, until the relatively distant time at which
enough mechanical wear in I/O devices and thermal-cycling stress in
components has accumulated for the machine to start going senile). Up
to half of all chip and wire failures happen within a new system's
first few weeks; such failures are often referred to as `infant
mortality' problems (or, occasionally, as `sudden infant death
syndrome'). See bathtub curve, burn-in period.
Node:infinite, Next:infinite loop, Previous:infant
mortality, Up:= I =
[common] Consisting of a large number of objects; extreme. Used very
loosely as in: "This program produces infinite garbage." "He is an
infinite loser." The word most likely to follow `infinite', though, is
hair. (It has been pointed out that fractals are an excellent
example of infinite hair.) These uses are abuses of the word's
mathematical meaning. The term `semi-infinite', denoting an
immoderately large amount of some resource, is also heard. "This
compiler is taking a semi-infinite amount of time to optimize my
program." See also semi.
Node:infinite loop, Next:Infinite-Monkey Theorem,
Previous:infinite, Up:= I =
infinite loop n.
One that never terminates (that is, the machine spins or
buzzes forever and goes catatonic). There is a standard
joke that has been made about each generation's exemplar of the
ultra-fast machine: "The Cray-3 is so fast it can execute an infinite
loop in under 2 seconds!"
Node:Infinite-Monkey Theorem, Next:infinity,
Previous:infinite loop, Up:= I =
Infinite-Monkey Theorem n.
"If you put an infinite number of monkeys at typewriters,
eventually one will bash out the script for Hamlet." (One may also
hypothesize a small number of monkeys and a very long period of time.)
This theorem asserts nothing about the intelligence of the one
random monkey that eventually comes up with the script (and note
that the mob will also type out all the possible incorrect versions of
Hamlet). It may be referred to semi-seriously when justifying a
brute force method; the implication is that, with enough
resources thrown at it, any technical challenge becomes a
one-banana problem. This argument gets more respect since
Linux justified the bazaar mode of development.
This theorem was first popularized by the astronomer Sir Arthur
Eddington. It became part of the idiom of techies via the classic SF
short story "Inflexible Logic" by Russell Maloney, and many younger
hackers know it through a reference in Douglas Adams's "Hitchhiker's
Guide to the Galaxy". On 1 April 2000 the usage acquired its own
Internet standard, http://www.rfc-editor.org/rfc/rfc2795.txt
(Infinite Monkey Protocol Suite).
Node:infinity, Next:inflate, Previous:Infinite-Monkey
Theorem, Up:= I =
1. The largest value that can be represented in a particular type of
variable (register, memory location, data type, whatever). 2. `minus
infinity': The smallest such value, not necessarily or even usually
the simple negation of plus infinity. In N-bit twos-complement
arithmetic, infinity is 2^(N-1) - 1 but minus infinity is - (2^(N-1)),
not -(2^(N-1) - 1). Note also that this is different from time T
equals minus infinity, which is closer to a mathematician's usage of
Node:inflate, Next:Infocom, Previous:infinity, Up:=
To decompress or puff a file. Rare among Internet hackers, used
primarily by MS-DOS/Windows types.
Node:Infocom, Next:initgame, Previous:inflate, Up:=
A now-legendary games company, active from 1979 to 1989, that
commercialized the MDL parser technology used for Zork to
produce a line of text adventure games that remain favorites among
hackers. Infocom's games were intelligent, funny, witty, erudite,
irreverent, challenging, satirical, and most thoroughly hackish in
spirit. The physical game packages from Infocom are now prized
collector's items. After being acquired by Activision in 1989 they did
a few more "modern" (e.g. graphics-intensive) games which were less
successful than reissues of their classics.
The software, thankfully, is still extant; Infocom games were written
in a kind of P-code and distributed with a P-code interpreter core,
and not only freeware emulators for that interpreter but an actual
compiler as well have been written to permit the P-code to be run on
platforms the games never originally graced. In fact, new games
written in this P-code are still bering written. (Emulators that can
run Infocom game ZIPs, and new games, are available at
Node:initgame, Next:insanely great, Previous:Infocom,
Up:= I =
initgame /in-it'gaym/ n.
[IRC] An IRC version of the trivia game "Botticelli", in which
one user changes his nick to the initials of a famous person or
other named entity, and the others on the channel ask yes or no
questions, with the one to guess the person getting to be "it" next.
As a courtesy, the one picking the initials starts by providing a
4-letter hint of the form sex, nationality, life-status,
reality-status. For example, MAAR means "Male, American, Alive, Real"
(as opposed to "fictional"). Initgame can be surprisingly addictive.
See also hing.
[1996 update: a recognizable version of the initgame has become a
staple of some radio talk shows in the U.S. We had it first! - ESR]
Node:insanely great, Next:installfest, Previous:initgame,
Up:= I =
insanely great adj.
[Mac community, from Steve Jobs; also BSD Unix people via Bill Joy]
Something so incredibly elegant that it is imaginable only to
someone possessing the most puissant of hacker-natures.
Node:installfest, Next:INTERCAL, Previous:insanely great,
Up:= I =
[Linux community since c.1998] Common portmanteau word for
"installation festival"; Linux user groups frequently run these.
Computer users are invited to bring their machines to have Linux
installed on their machines. The idea is to get them painlessly over
the biggest hump in migrating to Linux, which is initially installing
and configuring it for the user's machine.
Node:INTERCAL, Next:interesting, Previous:installfest,
Up:= I =
INTERCAL /in't*r-kal/ n.
[said by the authors to stand for `Compiler Language With No
Pronounceable Acronym'] A computer language designed by Don Woods and
James Lyons in 1972. INTERCAL is purposely different from all other
computer languages in all ways but one; it is purely a written
language, being totally unspeakable. An excerpt from the INTERCAL
Reference Manual will make the style of the language clear:
It is a well-known and oft-demonstrated fact that a person whose
work is incomprehensible is held in high esteem. For example, if
one were to state that the simplest way to store a value of 65536
in a 32-bit INTERCAL variable is:
DO :1 <- #0$#256
any sensible programmer would say that that was absurd. Since this
is indeed the simplest method, the programmer would be made to look
foolish in front of his boss, who would of course have happened to
turn up, as bosses are wont to do. The effect would be no less
devastating for the programmer having been correct.
INTERCAL has many other peculiar features designed to make it even
more unspeakable. The Woods-Lyons implementation was actually used by
many (well, at least several) people at Princeton. The language has
been recently reimplemented as C-INTERCAL and is consequently enjoying
an unprecedented level of unpopularity; there is even an
alt.lang.intercal newsgroup devoted to the study and ... appreciation
of the language on Usenet.
Inevitably, INTERCAL has a home page on the Web:
http://www.tuxedo.org/~esr/intercal/. An extended version,
implemented in (what else?) Perl and adding object-oriented
features, is available at http://dd-sh.assurdo.com/INTERCAL. See
Node:interesting, Next:Internet, Previous:INTERCAL,
Up:= I =
In hacker parlance, this word has strong connotations of `annoying',
or `difficult', or both. Hackers relish a challenge, and enjoy
wringing all the irony possible out of the ancient Chinese curse "May
you live in interesting times". Oppose trivial,
Node:Internet, Next:Internet address,
Previous:interesting, Up:= I =
The mother of all networks. First incarnated beginning in 1969 as the
ARPANET, a U.S. Department of Defense research testbed. Though it has
been widely believed that the goal was to develop a network
architecture for military command-and-control that could survive
disruptions up to and including nuclear war, this is a myth; in fact,
ARPANET was conceived from the start as a way to get most economical
use out of then-scarce large-computer resources.
As originally imagined, ARPANET's major use would have been to support
what is now called remote login and more sophisticated forms of
distributed computing, but the infant technology of electronic mail
quickly grew to dominate actual usage. Universities, research labs and
defense contractors early discovered the Internet's potential as a
medium of communication between humans and linked up in steadily
increasing numbers, connecting together a quirky mix of academics,
techies, hippies, SF fans, hackers, and anarchists. The roots of this
lexicon lie in those early years.
Over the next quarter-century the Internet evolved in many ways. The
typical machine/OS combination moved from DEC PDP-10s and
PDP-20s, running TOPS-10 and TOPS-20, to PDP-11s and
VAXes and Suns running Unix, and in the 1990s to Unix on Intel
microcomputers. The Internet's protocols grew more capable, most
notably in the move from NCP/IP to TCP/IP in 1982 and the
implementation of Domain Name Service in 1983. It was around this time
that people began referring to the collection of interconnected
networks with ARPANET at its core as "the Internet".
The ARPANET had a fairly strict set of participation guidelines -
connected institutions had to be involved with a DOD-related research
project. By the mid-80s, many of the organizations clamoring to join
didn't fit this profile. In 1986, the National Science Foundation
built NSFnet to open up access to its five regional supercomputing
centers; NSFnet became the backbone of the Internet, replacing the
original ARPANET pipes (which were formally shut down in 1990).
Between 1990 and late 1994 the pieces of NSFnet were sold to major
telecommunications companies until the Internet backbone had gone
That year, 1994, was also the year the mainstream culture discovered
the Internet. Once again, the killer app was not the anticipated
one - rather, what caught the public imagination was the hypertext and
multimedia features of the World Wide Web. Subsequently the Internet
has seen off its only serious challenger (the OSI protocol stack
favored by European telecom monopolies) and is in the process of
absorbing into itself many of the proprietary networks built during
the second wave of wide-area networking after 1980. It is now (1996) a
commonplace even in mainstream media to predict that a
globally-extended Internet will become the key unifying communications
technology of the next century. See also the network and
Node:Internet address, Next:Internet Death Penalty,
Previous:Internet, Up:= I =
Internet address n.
1. [techspeak] An absolute network address of the form email@example.com,
where foo is a user name, bar is a sitename, and baz is a
`domain' name, possibly including periods itself. Contrast with
bang path; see also the network and network address.
All Internet machines and most UUCP sites can now resolve these
addresses, thanks to a large amount of behind-the-scenes magic and
PD software written since 1980 or so. See also bang path,
domainist. 2. More loosely, any network address reachable
through Internet; this includes bang path addresses and some
internal corporate and government networks.
Reading Internet addresses is something of an art. Here are the four
most important top-level functional Internet domains followed by a
selection of geographical domains:
U.S. government civilian sites
U.S. military sites
Note that most of the sites in the com and edu domains are in the U.S.
sites in the U.S. outside the functional domains
sites in the ex-Soviet Union (see kremvax).
sites in the United Kingdom
Within the us domain, there are subdomains for the fifty states, each
generally with a name identical to the state's postal abbreviation.
Within the uk domain, there is an ac subdomain for academic sites and
a co domain for commercial ones. Other top-level domains may be
divided up in similar ways.
Node:Internet Death Penalty, Next:Internet Exploder,
Previous:Internet address, Up:= I =
Internet Death Penalty
[Usenet] (often abbreviated IDP) The ultimate sanction against
spam-emitting sites - complete shunning at the router level of
all mail and packets, as well as Usenet messages, from the offending
domain(s). Compare Usenet Death Penalty, with which it is
Node:Internet Exploder, Next:Internet Exploiter,
Previous:Internet Death Penalty, Up:= I =
[very common] Pejorative hackerism for Microsoft's "Internet Explorer"
web browser (also "Internet Exploiter"). Compare HP-SUX,
AIDX, buglix, Macintrash, Telerat,
ScumOS, sun-stools, Slowlaris.
Node:Internet Exploiter, Next:interrupt, Previous:Internet
Exploder, Up:= I =
Internet Exploiter n.
Another common name-of-insult for Internet Explorer, Microsoft's
overweight Web Browser; more hostile than Internet Exploder.
Reflects widespread hostility to Microsoft and a sense that it is
seeking to hijack, monopolize, and corrupt the Internet. Compare
Exploder and the less pejorative Netscrape.
Node:interrupt, Next:interrupt list, Previous:Internet
Exploiter, Up:= I =
1. [techspeak] n. On a computer, an event that interrupts normal
processing and temporarily diverts flow-of-control through an
"interrupt handler" routine. See also trap. 2. interj. A request
for attention from a hacker. Often explicitly spoken. "Interrupt --
have you seen Joe recently?" See priority interrupt. 3. Under
MS-DOS, nearly synonymous with `system call', because the OS and BIOS
routines are both called using the INT instruction (see
interrupt list) and because programmers so often have to bypass
the OS (going directly to a BIOS interrupt) to get reasonable
Node:interrupt list, Next:interrupts locked out,
Previous:interrupt, Up:= I =
interrupt list n.
[MS-DOS] The list of all known software interrupt calls (both
documented and undocumented) for IBM PCs and compatibles, maintained
and made available for free redistribution by Ralf Brown
Usenetter infamous for various surrealist net.pranks and an uncanny,
machine-assisted knack for joining any thread in which his nom de
guerre is mentioned. He has a website at http://www.kibo.com/.
Node:kiboze, Next:kibozo, Previous:KIBO, Up:= K =
[Usenet] To grep the Usenet news for a string, especially with
the intention of posting a follow-up. This activity was popularised by
Kibo (see KIBO, sense 2).
Node:kibozo, Next:kick, Previous:kiboze, Up:= K =
kibozo /ki:-boh'zoh/ n.
[Usenet] One who kibozes but is not Kibo (see KIBO, sense
Node:kick, Next:kill file, Previous:kibozo, Up:= K =
1. [IRC] To cause somebody to be removed from a IRC channel, an
option only available to channel ops. This is an extreme measure,
often used to combat extreme flamage or flooding, but
sometimes used at the CHOP's whim. Compare gun. 2. To
reboot a machine or kill a running process. "The server's down, let me
go kick it."
Node:kill file, Next:killer app, Previous:kick, Up:=
kill file n.
[Usenet; very common] (alt. `KILL file') Per-user file(s) used by some
Usenet reading programs (originally Larry Wall's rn(1)) to
discard summarily (without presenting for reading) articles matching
some particularly uninteresting (or unwanted) patterns of subject,
author, or other header lines. Thus to add a person (or subject) to
one's kill file is to arrange for that person to be ignored by one's
newsreader in future. By extension, it may be used for a decision to
ignore the person or subject in other media. See also plonk.
Node:killer app, Next:killer micro, Previous:kill file,
Up:= K =
The application that actually makes a sustaining market for a
promising but under-utilized technology. First used in the mid-1980s
to describe Lotus 1-2-3 once it became evident that demand for that
product had been the major driver of the early business market for IBM
PCs. The term was then restrospectively applied to VisiCalc, which had
played a similar role in the success of the Apple II. After 1994 it
became commonplace to describe the World Wide Web as the Internet's
killer app. One of the standard questions asked about each new
personal-computer technology as it emerges has become "what's the
Node:killer micro, Next:killer poke, Previous:killer app,
Up:= K =
killer micro n.
[popularized by Eugene Brooks] A microprocessor-based machine that
infringes on mini, mainframe, or supercomputer performance turf. Often
heard in "No one will survive the attack of the killer micros!", the
battle cry of the downsizers. Used esp. of RISC architectures.
The popularity of the phrase `attack of the killer micros' is
doubtless reinforced by the title of the movie "Attack Of The Killer
Tomatoes" (one of the canonical examples of
so-bad-it's-wonderful among hackers). This has even more flavor
now that killer micros have gone on the offensive not just
individually (in workstations) but in hordes (within massively
[1996 update: Eugene Brooks was right. Since this term first entered
the Jargon File in 1990, the minicomputer has effectively vanished,
the mainframe sector is in deep and apparently terminal decline
(with IBM but a shadow of its former self), and even the supercomputer
business has contracted into a smaller niche. It's networked killer
micros as far as the eye can see. --ESR]
Node:killer poke, Next:kilo-, Previous:killer micro,
Up:= K =
killer poke n.
A recipe for inducing hardware damage on a machine via insertion of
invalid values (see poke) into a memory-mapped control register;
used esp. of various fairly well-known tricks on bitty boxes
without hardware memory management (such as the IBM PC and Commodore
PET) that can overload and trash analog electronics in the monitor.
See also HCF.
Node:kilo-, Next:KIPS, Previous:killer poke, Up:= K
[SI] See quantifiers.
Node:KIPS, Next:KISS Principle, Previous:kilo-, Up:=
KIPS /kips/ n.
[abbreviation, by analogy with MIPS using K] Thousands
(not 1024s) of Instructions Per Second. Usage: rare.
Node:KISS Principle, Next:kit, Previous:KIPS, Up:= K
KISS Principle /kis' prin'si-pl/ n.
"Keep It Simple, Stupid". A maxim often invoked when discussing design
to fend off creeping featurism and control development
complexity. Possibly related to the marketroid maxim on sales
presentations, "Keep It Short and Simple".
Node:kit, Next:klone, Previous:KISS Principle, Up:=
[Usenet; poss. fr. DEC slang for a full software distribution,
as opposed to a patch or upgrade] A source software distribution that
has been packaged in such a way that it can (theoretically) be
unpacked and installed according to a series of steps using only
standard Unix tools, and entirely documented by some reasonable chain
of references from the top-level README file. The more general
term distribution may imply that special tools or more stringent
conditions on the host environment are required.
Node:klone, Next:kludge, Previous:kit, Up:= K =
klone /klohn/ n.
See clone, sense 4.
Node:kludge, Next:kluge, Previous:klone, Up:= K =
kludge 1. /klooj/ n.
Incorrect (though regrettably common) spelling of kluge (US).
These two words have been confused in American usage since the early
1960s, and widely confounded in Great Britain since the end of World
War II. 2. [TMRC] A crock that works. (A long-ago "Datamation"
article by Jackson Granholme similarly said: "An ill-assorted
collection of poorly matching parts, forming a distressing whole.") 3.
v. To use a kludge to get around a problem. "I've kludged around it
for now, but I'll fix it up properly later."
This word appears to have derived from Scots `kludge' or `kludgie' for
a common toilet, via British military slang. It apparently became
confused with U.S. kluge during or after World War II; some
Britons from that era use both words in definably different ways, but
kluge is now uncommon in Great Britain. `Kludge' in Commonwealth
hackish differs in meaning from `kluge' in that it lacks the positive
senses; a kludge is something no Commonwealth hacker wants to be
associated too closely with. Also, `kludge' is more widely known in
British mainstream slang than `kluge' is in the U.S.
Node:kluge, Next:kluge around, Previous:kludge, Up:=
[from the German `klug', clever; poss. related to Polish `klucz' (a
key, a hint, a main point)] 1. n. A Rube Goldberg (or Heath Robinson)
device, whether in hardware or software. 2. n. A clever programming
trick intended to solve a particular nasty case in an expedient, if
not clear, manner. Often used to repair bugs. Often involves
ad-hockery and verges on being a crock. 3. n. Something
that works for the wrong reason. 4. vt. To insert a kluge into a
program. "I've kluged this routine to get around that weird bug, but
there's probably a better way." 5. [WPI] n. A feature that is
implemented in a rude manner.
Nowadays this term is often encountered in the variant spelling
`kludge'. Reports from old farts are consistent that `kluge' was
the original spelling, reported around computers as far back as the
mid-1950s and, at that time, used exclusively of hardware kluges. In
1947, the "New York Folklore Quarterly" reported a classic shaggy-dog
story `Murgatroyd the Kluge Maker' then current in the Armed Forces,
in which a `kluge' was a complex and puzzling artifact with a trivial
function. Other sources report that `kluge' was common Navy slang in
the WWII era for any piece of electronics that worked well on shore
but consistently failed at sea.
However, there is reason to believe this slang use may be a decade
older. Several respondents have connected it to the brand name of a
device called a "Kluge paper feeder", an adjunct to mechanical
printing presses. Legend has it that the Kluge feeder was designed
before small, cheap electric motors and control electronics; it relied
on a fiendishly complex assortment of cams, belts, and linkages to
both power and synchronize all its operations from one motive
driveshaft. It was accordingly temperamental, subject to frequent
breakdowns, and devilishly difficult to repair -- but oh, so clever!
People who tell this story also aver that `Kluge' was the name of a
There is in fact a Brandtjen & Kluge Inc., an old family business that
manufactures printing equipment - interestingly, their name is
pronounced /kloo'gee/! Henry Brandtjen, president of the firm, told me
(ESR, 1994) that his company was co-founded by his father and an
engineer named Kluge /kloo'gee/, who built and co-designed the
original Kluge automatic feeder in 1919. Mr. Brandtjen claims,
however, that this was a simple device (with only four cams); he says
he has no idea how the myth of its complexity took hold.
TMRC and the MIT hacker culture of the early '60s seems to have
developed in a milieu that remembered and still used some WWII
military slang (see also foobar). It seems likely that `kluge'
came to MIT via alumni of the many military electronics projects that
had been located in Cambridge (many in MIT's venerable Building 20, in
which TMRC is also located) during the war.
The variant `kludge' was apparently popularized by the
Datamation article mentioned above; it was titled "How to Design
a Kludge" (February 1962, pp. 30, 31). This spelling was probably
imported from Great Britain, where kludge has an independent
history (though this fact was largely unknown to hackers on either
side of the Atlantic before a mid-1993 debate in the Usenet group
alt.folklore.computers over the First and Second Edition versions of
this entry; everybody used to think kludge was just a mutation
of kluge). It now appears that the British, having forgotten the
etymology of their own `kludge' when `kluge' crossed the Atlantic,
repaid the U.S. by lobbing the `kludge' orthography in the other
direction and confusing their American cousins' spelling!
The result of this history is a tangle. Many younger U.S. hackers
pronounce the word as /klooj/ but spell it, incorrectly for its
meaning and pronunciation, as `kludge'. (Phonetically, consider huge,
refuge, centrifuge, and deluge as opposed to sludge, judge, budge, and
fudge. Whatever its failings in other areas, English spelling is
perfectly consistent about this distinction.) British hackers mostly
learned /kluhj/ orally, use it in a restricted negative sense and are
at least consistent. European hackers have mostly learned the word
from written American sources and tend to pronounce it /kluhj/ but use
the wider American meaning!
Some observers consider this mess appropriate in view of the word's
Node:kluge around, Next:kluge up, Previous:kluge,
Up:= K =
kluge around vt.
To avoid a bug or difficult condition by inserting a kluge.
Node:kluge up, Next:Knights of the Lambda Calculus,
Previous:kluge around, Up:= K =
kluge up vt.
To lash together a quick hack to perform a task; this is milder than
cruft together and has some of the connotations of hack up
(note, however, that the construction `kluge on' corresponding to
hack on is never used). "I've kluged up this routine to dump the
buffer contents to a safe place."
Node:Knights of the Lambda Calculus, Next:knobs,
Previous:kluge up, Up:= K =
Knights of the Lambda Calculus n.
A semi-mythical organization of wizardly LISP and Scheme hackers. The
name refers to a mathematical formalism invented by Alonzo Church,
with which LISP is intimately connected. There is no enrollment list
and the criteria for induction are unclear, but one well-known LISPer
has been known to give out buttons and, in general, the members know
who they are....
Node:knobs, Next:Knuth, Previous:Knights of the Lambda
Calculus, Up:= K =
Configurable options, even in software and even those you can't adjust
in real time. Anything you can twiddle is a knob. "Has this PNG
viewer got an alpha knob?" Software may be described as having "knobs
and switches" or occasionally "knobs and lights".
Node:Knuth, Next:koan, Previous:knobs, Up:= K =
Knuth /ka-nooth'/ n.
[Donald E. Knuth's "The Art of Computer Programming"] Mythically, the
reference that answers all questions about data structures or
algorithms. A safe answer when you do not know: "I think you can find
that in Knuth." Contrast the literature. See also bible.
There is a Donald Knuth home page at
Node:koan, Next:kremvax, Previous:Knuth, Up:= K =
koan /koh'an/ n.
A Zen teaching riddle. Classically, koans are attractive paradoxes to
be meditated on; their purpose is to help one to enlightenment by
temporarily jamming normal cognitive processing so that something more
interesting can happen (this practice is associated with Rinzei Zen
Buddhism). Hackers are very fond of the koan form and compose their
own koans for humororous and/or enlightening effect. See Some AI
Koans, has the X nature, hacker humor.
Node:kremvax, Next:kyrka, Previous:koan, Up:= K =
kremvax /krem-vaks/ n.
[from the then large number of Usenet VAXen with names of
the form foovax] Originally, a fictitious Usenet site at the Kremlin,
announced on April 1, 1984 in a posting ostensibly originated there by
Soviet leader Konstantin Chernenko. The posting was actually forged by
Piet Beertema as an April Fool's joke. Other fictitious sites
mentioned in the hoax were moskvax and kgbvax. This was probably
the funniest of the many April Fool's forgeries perpetrated on Usenet
(which has negligible security against them), because the notion that
Usenet might ever penetrate the Iron Curtain seemed so totally absurd
at the time.
In fact, it was only six years later that the first genuine site in
Moscow, demos.su, joined Usenet. Some readers needed convincing that
the postings from it weren't just another prank. Vadim Antonov, senior
programmer at Demos and the major poster from there up to mid-1991,
was quite aware of all this, referred to it frequently in his own
postings, and at one point twitted some credulous readers by blandly
asserting that he was a hoax!
Eventually he even arranged to have the domain's gateway site named
kremvax, thus neatly turning fiction into fact and demonstrating that
the hackish sense of humor transcends cultural barriers. [Mr. Antonov
also contributed the Russian-language material for this lexicon.
In an even more ironic historical footnote, kremvax became an
electronic center of the anti-communist resistance during the bungled
hard-line coup of August 1991. During those three days the Soviet UUCP
network centered on kremvax became the only trustworthy news source
for many places within the USSR. Though the sysops were concentrating
on internal communications, cross-border postings included immediate
transliterations of Boris Yeltsin's decrees condemning the coup and
eyewitness reports of the demonstrations in Moscow's streets. In those
hours, years of speculation that totalitarianism would prove unable to
maintain its grip on politically-loaded information in the age of
computer networking were proved devastatingly accurate -- and the
original kremvax joke became a reality as Yeltsin and the new Russian
revolutionaries of `glasnost' and `perestroika' made kremvax one of
the timeliest means of their outreach to the West.
Node:kyrka, Next:lace card, Previous:kremvax, Up:= K
kyrka /chur'ka/ n.
[Swedish] See feature key.
Node:= L =, Next:= M =, Previous:= K =, Up:The
= L =
* lace card:
* language lawyer:
* languages of choice:
* larval stage:
* laser chicken:
* leaf site:
* leaky heap:
* leapfrog attack:
* leech mode:
* let the smoke out:
* Life is hard:
* light pipe:
* like kicking dead whales down the beach:
* like nailing jelly to a tree:
* line 666:
* line eater the:
* line noise:
* line starve:
* link farm:
* link rot:
* lion food:
* Lions Book:
* lithium lick:
* live data:
* Live Free Or Die!:
* locals the:
* locked and loaded:
* locked up:
* logic bomb:
* loop through:
* loose bytes:
* lord high fixer:
* lose lose:
* lost in the noise:
* lost in the underflow:
* lots of MIPS but no I/O:
* Lubarsky's Law of Cybernetic Entomology:
* Lumber Cartel:
* lunatic fringe:
Node:lace card, Next:lag, Previous:kyrka, Up:= L =
lace card n. obs.
A punched card with all holes punched (also called a `whoopee
card' or `ventilator card'). Card readers tended to jam when they got
to one of these, as the resulting card had too little structural
strength to avoid buckling inside the mechanism. Card punches could
also jam trying to produce these things owing to power-supply
problems. When some practical joker fed a lace card through the
reader, you needed to clear the jam with a `card knife' -- which you
used on the joker first.
Node:lag, Next:lamer, Previous:lace card, Up:= L =
[MUD, IRC; very common] When used without qualification this is
synomous with netlag. Curiously, people will often complain "I'm
really lagged" when in fact it is their server or network connection
that is lagging.
Node:lamer, Next:language lawyer, Previous:lag, Up:=
[prob. originated in skateboarder slang] 1. Synonym for luser,
not used much by hackers but common among warez d00dz, crackers,
and phreakers. A person who downloads much, but who never
uploads. (Also known as `leecher'). Oppose elite. Has the same
connotations of self-conscious elitism that use of luser does
among hackers. 2. Someone who tries to crack a BBS. 3. Someone who
annoys the sysop or other BBS users - for instance, by posting lots of
silly messages, uploading virus-ridden software, frequently dropping
Crackers also use it to refer to cracker wannabees. In phreak
culture, a lamer is one who scams codes off others rather than doing
cracks or really understanding the fundamental concepts. In
warez d00dz culture, where the ability to wave around cracked
commercial software within days of (or before) release to the
commercial market is much esteemed, the lamer might try to upload
garbage or shareware or something incredibly old (old in this context
is read as a few years to anything older than 3 days).
`Lamer' is also much used in the IRC world in a similar sense to the
Node:language lawyer, Next:languages of choice,
Previous:lamer, Up:= L =
language lawyer n.
A person, usually an experienced or senior software engineer, who is
intimately familiar with many or most of the numerous restrictions and
features (both useful and esoteric) applicable to one or more computer
programming languages. A language lawyer is distinguished by the
ability to show you the five sentences scattered through a
200-plus-page manual that together imply the answer to your question
"if only you had thought to look there". Compare wizard,
Node:languages of choice, Next:LART, Previous:language
lawyer, Up:= L =
languages of choice n.
C, C++, LISP, and Perl. Nearly every hacker
knows one of C or LISP, and most good ones are fluent in both. C++,
despite some serious drawbacks, is generally preferred to other
object-oriented languages (though in 1999 it looks as though
Java has displaced it in the affections of hackers, if not
everywhere). Since around 1990 Perl has rapidly been gaining favor,
especially as a tool for systems-administration utilities and rapid
prototyping. Python, Smalltalk and Prolog are also popular in
small but influential communities.
There is also a rapidly dwindling category of older hackers with
FORTRAN, or even assembler, as their language of choice. They often
prefer to be known as Real Programmers, and other hackers
consider them a bit odd (see "The Story of Mel" in Appendix A).
Assembler is generally no longer considered interesting or appropriate
for anything but HLL implementation, glue, and a few
time-critical and hardware-specific uses in systems programs. FORTRAN
occupies a shrinking niche in scientific programming.
Most hackers tend to frown on languages like Pascal and
Ada, which don't give them the near-total freedom considered
necessary for hacking (see bondage-and-discipline language), and
to regard everything even remotely connected with COBOL or other
traditional card walloper languages as a total and unmitigated
Node:LART, Next:larval stage, Previous:languages of
choice, Up:= L =
Luser Attitude Readjustment Tool. 1. n. In the collective mythos of
scary devil monastery, this is an essential item in the toolkit
of every BOFH. The LART classic is a 2x4 or other large billet
of wood usable as a club, to be applied upside the head of spammers
and other people who cause sysadmins more grief than just naturally
goes with the job. Perennial debates rage on alt.sysadmin.recovery
over what constitutes the truly effective LART; knobkerries,
semiautomatic weapons, flamethrowers, and tactical nukes all have
their partisans. Compare clue-by-four. 2. v. To use a LART. Some
would add "in malice", but some sysadmins do prefer to gently lart
their users as a first (and sometimes final) warning. 3. interj.
Calling for one's LART, much as a surgeon might call "Scalpel!". 4.
interj. [rare] Used in flames as a rebuke. "LART! LART! LART!"
Node:larval stage, Next:lase, Previous:LART, Up:= L
larval stage n.
Describes a period of monomaniacal concentration on coding apparently
passed through by all fledgling hackers. Common symptoms include the
perpetration of more than one 36-hour hacking run in a given
week; neglect of all other activities including usual basics like
food, sleep, and personal hygiene; and a chronic case of advanced
bleary-eye. Can last from 6 months to 2 years, the apparent median
being around 18 months. A few so afflicted never resume a more
`normal' life, but the ordeal seems to be necessary to produce really
wizardly (as opposed to merely competent) programmers. See also
wannabee. A less protracted and intense version of larval stage
(typically lasting about a month) may recur when one is learning a new
OS or programming language.
Node:lase, Next:laser chicken, Previous:larval stage,
Up:= L =
lase /layz/ vt.
To print a given document via a laser printer. "OK, let's lase that
sucker and see if all those graphics-macro calls did the right
Node:laser chicken, Next:lasherism, Previous:lase,
Up:= L =
laser chicken n.
Kung Pao Chicken, a standard Chinese dish containing chicken, peanuts,
and hot red peppers in a spicy pepper-oil sauce. Many hackers call it
`laser chicken' for two reasons: It can zap you just like a
laser, and the sauce has a red color reminiscent of some laser beams.
The dish has also been called `gunpowder chicken'.
In a variation on this theme, it is reported that some Australian
hackers have redesignated the common dish `lemon chicken' as
`Chernobyl Chicken'. The name is derived from the color of the sauce,
which is considered bright enough to glow in the dark (as, mythically,
do some of the inhabitants of Chernobyl).
Node:lasherism, Next:laundromat, Previous:laser chicken,
Up:= L =
[Harvard] A program that solves a standard problem (such as the Eight
Queens puzzle or implementing the life algorithm) in a
deliberately nonstandard way. Distinguished from a crock or
kluge by the fact that the programmer did it on purpose as a
mental exercise. Such constructions are quite popular in exercises
such as the Obfuscated C Contest, and occasionally in
retrocomputing. Lew Lasher was a student at Harvard around 1980
who became notorious for such behavior.
Node:laundromat, Next:LDB, Previous:lasherism, Up:=
Syn. disk farm; see washing machine.
Node:LDB, Next:leaf site, Previous:laundromat, Up:=
LDB /l*'d*b/ vt.
[from the PDP-10 instruction set] To extract from the middle. "LDB me
a slice of cake, please." This usage has been kept alive by Common
LISP's function of the same name. Considered silly. See also
Node:leaf site, Next:leak, Previous:LDB, Up:= L =
leaf site n.,obs.
Before pervasive TCP/IP, this term was used of a machine that merely
originated and read Usenet news or mail, and did not relay any
third-party traffic. It was often uttered in a critical tone; when the
ratio of leaf sites to backbone, rib, and other relay sites got too
high, the network tended to develop bottlenecks. Compare
backbone site, rib site. Now that traffic patterns depend
more on the distribution of routers than of host machines this term
has largely fallen out of use.
Node:leak, Next:leaky heap, Previous:leaf site, Up:=
With qualifier, one of a class of resource-management bugs that occur
when resources are not freed properly after operations on them are
finished, so they effectively disappear (leak out). This leads to
eventual exhaustion as new allocation requests come in. memory
leak and fd leak have their own entries; one might also refer,
to, say, a `window handle leak' in a window system.
Node:leaky heap, Next:leapfrog attack, Previous:leak,
Up:= L =
leaky heap n.
[Cambridge] An arena with a memory leak.
Node:leapfrog attack, Next:leech, Previous:leaky heap,
Up:= L =
leapfrog attack n.
Use of userid and password information obtained illicitly from one
host (e.g., downloading a file of account IDs and passwords, tapping
TELNET, etc.) to compromise another host. Also, the act of TELNETting
through one or more hosts in order to confuse a trace (a standard
Node:leech, Next:leech mode, Previous:leapfrog attack,
Up:= L =
1. n. (Also `leecher'.) Among BBS types, crackers and warez
d00dz, one who consumes knowledge without generating new software,
cracks, or techniques. BBS culture specifically defines a leech as
someone who downloads files with few or no uploads in return, and who
does not contribute to the message section. Cracker culture extends
this definition to someone (a lamer, usually) who constantly
presses informed sources for information and/or assistance, but has
nothing to contribute. 2. v. [common, Toronto area] To instantly fetch
a file (other than a mail attachment) whether by FTP or IRC file req
or any other method. Seems to be a holdover from the early 1990s when
Toronto had a very active BBS and warez scene.
Node:leech mode, Next:legal, Previous:leech, Up:= L
leech mode n.
[warez d00dz] "Leech mode" or "leech access" or (simply "leech" as in
"You get leech") is the access mode on a FTP site where one can
download as many files as one wants, without having to upload. Leech
mode is often promised on banner sites, but rarely obtained. See
ratio site, banner site.
Node:legal, Next:legalese, Previous:leech mode, Up:=
Loosely used to mean `in accordance with all the relevant rules', esp.
in connection with some set of constraints defined by software. "The
older =+ alternate for += is no longer legal syntax in ANSI C." "This
parser processes each line of legal input the moment it sees the
trailing linefeed." Hackers often model their work as a sort of game
played with the environment in which the objective is to maneuver
through the thicket of `natural laws' to achieve a desired objective.
Their use of `legal' is flavored as much by this game-playing sense as
by the more conventional one having to do with courts and lawyers.
Compare language lawyer, legalese.
Node:legalese, Next:LER, Previous:legal, Up:= L =
Dense, pedantic verbiage in a language description, product
specification, or interface standard; text that seems designed to
obfuscate and requires a language lawyer to parse it.
Though hackers are not afraid of high information density and
complexity in language (indeed, they rather enjoy both), they share a
deep and abiding loathing for legalese; they associate it with
deception, suits, and situations in which hackers generally get
the short end of the stick.
Node:LER, Next:LERP, Previous:legalese, Up:= L =
n. 1. [TMRC, from `Light-Emitting Diode'] A light-emitting resistor
(that is, one in the process of burning up). Ohm's law was broken. See
also SED. 2. An incandescent light bulb (the filament emits
light because it's resistively heated).
Node:LERP, Next:let the smoke out, Previous:LER,
Up:= L =
LERP /lerp/ vi.,n.
Quasi-acronym for Linear Interpolation, used as a verb or noun for the
operation. "Bresenham's algorithm lerps incrementally between the two
endpoints of the line."
Node:let the smoke out, Next:letterbomb, Previous:LERP,
Up:= L =
let the smoke out v.
To fry hardware (see fried). See magic smoke for a
discussion of the underlying mythology.
Node:letterbomb, Next:lexer, Previous:let the smoke out,
Up:= L =
1. n. A piece of email containing live data intended to do
nefarious things to the recipient's machine or terminal. It used to be
possible, for example, to send letterbombs that would lock up some
specific kinds of terminals when they are viewed, so thoroughly that
the user must cycle power (see cycle, sense 3) to unwedge them.
Under Unix, a letterbomb can also try to get part of its contents
interpreted as a shell command to the mailer. The results of this
could range from silly to tragic; fortunately it has been some years
since any of the standard Unix/Internet mail software was vulnerable
to such an attack (though, as the Melissa virus attack demonstrated in
early 1999, Microsoft systems can have serious problems). See also
Trojan horse; compare nastygram. 2. Loosely, a
Node:lexer, Next:lexiphage, Previous:letterbomb,
Up:= L =
lexer /lek'sr/ n.
Common hacker shorthand for `lexical analyzer', the input-tokenizing
stage in the parser for a language (the part that breaks it into
word-like pieces). "Some C lexers get confused by the old-style
compound ops like =-."
Node:lexiphage, Next:life, Previous:lexer, Up:= L =
lexiphage /lek'si-fayj`/ n.
A notorious word chomper on ITS. See bagbiter. This
program would draw on a selected victim's bitmapped terminal the words
"THE BAG" in ornate letters, followed a pair of jaws biting pieces of
Node:life, Next:Life is hard, Previous:lexiphage,
Up:= L =
1. A cellular-automata game invented by John Horton Conway and first
introduced publicly by Martin Gardner ("Scientific American", October
1970); the game's popularity had to wait a few years for computers on
which it could reasonably be played, as it's no fun to simulate the
cells by hand. Many hackers pass through a stage of fascination with
it, and hackers at various places contributed heavily to the
mathematical analysis of this game (most notably Bill Gosper at MIT,
who even implemented life in TECO!; see Gosperism). When a
hacker mentions `life', he is much more likely to mean this game than
the magazine, the breakfast cereal, or the human state of existence.
2. The opposite of Usenet. As in "Get a life!"
Node:Life is hard, Next:light pipe, Previous:life,
Up:= L =
Life is hard prov.
[XEROX PARC] This phrase has two possible interpretations: (1) "While
your suggestion may have some merit, I will behave as though I hadn't
heard it." (2) "While your suggestion has obvious merit, equally
obvious circumstances prevent it from being seriously considered." The
charm of the phrase lies precisely in this subtle but important
Node:light pipe, Next:lightweight, Previous:Life is hard,
Up:= L =
light pipe n.
Fiber optic cable. Oppose copper.
Node:lightweight, Next:like kicking dead whales down the beach,
Previous:light pipe, Up:= L =
Opposite of heavyweight; usually found in combining forms such
as `lightweight process'.
Node:like kicking dead whales down the beach, Next:like nailing
jelly to a tree, Previous:lightweight, Up:= L =
like kicking dead whales down the beach adj.
Describes a slow, difficult, and disgusting process. First popularized
by a famous quote about the difficulty of getting work done under one
of IBM's mainframe OSes. "Well, you could write a C compiler in COBOL,
but it would be like kicking dead whales down the beach." See also
fear and loathing.
Node:like nailing jelly to a tree, Next:line 666,
Previous:like kicking dead whales down the beach, Up:= L =
like nailing jelly to a tree adj.
Used to describe a task thought to be impossible, esp. one in which
the difficulty arises from poor specification or inherent slipperiness
in the problem domain. "Trying to display the `prettiest' arrangement
of nodes and arcs that diagrams a given graph is like nailing jelly to