The Hacker's Dictionary by - (romantic novels to read TXT) 📖

cool down an object by placing it in the path of a computron beam. It is believed that this may also explain why machines that work at the factory fail in the computer room: the computrons there have been all used up by the other hardware.

(This theory probably owes something to the "Warlock" stories by Larry Niven, the best known being "What Good is a Glass Dagger?", in which magic is fueled by an exhaustible natural resource called `mana'.)

:condition out: vt. To prevent a section of code from being compiled by surrounding it with a conditional-compilation directive whose condition is always false. The {canonical} examples are #if 0' (or#ifdef notdef', though some find this {bletcherous}) and `#endif' in C. Compare {comment out}.

:condom: n. 1. The protective plastic bag that accompanies 3.5-inch microfloppy diskettes. Rarely, also used of (paper) disk envelopes. Unlike the write protect tab, the condom (when left on) not only impedes the practice of {SEX} but has also been shown to have a high failure rate as drive mechanisms attempt to access the disk --- and can even fatally frustrate insertion. 2. The protective cladding on a {light pipe}.

:confuser: n. Common soundalike slang for computer'. Usually encountered in compounds such asconfuser room', personal confuser',confuser guru'. Usage: silly.

:connector conspiracy: [probably came into prominence with the appearance of the KL-10 (one model of the {PDP-10}), none of whose connectors matched anything else] n. The tendency of manufacturers (or, by extension, programmers or purveyors of anything) to come up with new products that don't fit together with the old stuff, thereby making you buy either all new stuff or expensive interface devices. The KL-10 Massbus connector was actually patented by DEC, which reputedly refused to license the design and thus effectively locked third parties out of competition for the lucrative Massbus peripherals market. This is a source of never-ending frustration for the diehards who maintain older PDP-10 or VAX systems. Their CPUs work fine, but they are stuck with dying, obsolescent disk and tape drives with low capacity and high power requirements.

(A closely related phenomenon, with a slightly different intent, is the habit manufacturers have of inventing new screw heads so that only Designated Persons, possessing the magic screwdrivers, can remove covers and make repairs or install options. The Apple Macintosh takes this one step further, requiring not only a hex wrench but a specialized case-cracking tool to open the box.) In these latter days of open-systems computing this term has fallen somewhat into disuse, to be replaced by the observation that "Standards are great! There are so many of them to choose from!" Compare {backward combatability}.

:cons: /konz/ or /kons/ [from LISP] 1. vt. To add a new element to a specified list, esp. at the top. "OK, cons picking a replacement for the console TTY onto the agenda." 2. `cons up': vt. To synthesize from smaller pieces: "to cons up an example".

In LISP itself, cons' is the most fundamental operation for building structures. It takes any two objects and returns adot-pair' or two-branched tree with one object hanging from each branch. Because the result of a cons is an object, it can be used to build binary trees of any shape and complexity. Hackers think of it as a sort of universal constructor, and that is where the jargon meanings spring from.

:considered harmful: adj. Edsger W. Dijkstra's note in the March 1968 `Communications of the ACM', "Goto Statement Considered Harmful", fired the first salvo in the structured programming wars. Amusingly, the ACM considered the resulting acrimony sufficiently harmful that it will (by policy) no longer print an article taking so assertive a position against a coding practice. In the ensuing decades, a large number of both serious papers and parodies have borne titles of the form "X

considered Y". The structured-programming wars eventually blew over with the realization that both sides were wrong, but use of such titles has remained as a persistent minor in-joke (the `considered silly' found at various places in this lexicon is related).

:console:: n. 1. The operator's station of a {mainframe}. In times past, this was a privileged location that conveyed godlike powers to anyone with fingers on its keys. Under UNIX and other modern timesharing OSes, such privileges are guarded by passwords instead, and the console is just the {tty} the system was booted from. Some of the mystique remains, however, and it is traditional for sysadmins to post urgent messages to all users from the console (on UNIX, /dev/console). 2. On microcomputer UNIX boxes, the main screen and keyboard (as opposed to character-only terminals talking to a serial port). Typically only the console can do real graphics or run {X}. See also {CTY}.

:console jockey: n. See {terminal junkie}.

:content-free: [by analogy with techspeak `context-free'] adj.

Used of a message that adds nothing to the recipient's knowledge.

Though this adjective is sometimes applied to {flamage}, it more usually connotes derision for communication styles that exalt form over substance or are centered on concerns irrelevant to the subject ostensibly at hand. Perhaps most used with reference to speeches by company presidents and other professional manipulators.

"Content-free? Uh...that's anything printed on glossy paper." See also {four-color glossies}. "He gave a talk on the implications of electronic networks for postmodernism and the fin-de-siecle aesthetic. It was content-free."

:control-C: vi. 1. "Stop whatever you are doing." From the interrupt character used on many operating systems to abort a running program. Considered silly. 2. interj. Among BSD UNIX

hackers, the canonical humorous response to "Give me a break!"

:control-O: vi. "Stop talking." From the character used on some operating systems to abort output but allow the program to keep on running. Generally means that you are not interested in hearing anything more from that person, at least on that topic; a standard response to someone who is flaming. Considered silly. Compare {control-S}.

:control-Q: vi. "Resume." From the ASCII DC1 or {XON}

character (the pronunciation /X-on/ is therefore also used), used to undo a previous {control-S}.

:control-S: vi. "Stop talking for a second." From the ASCII DC3

or XOFF character (the pronunciation /X-of/ is therefore also used). Control-S differs from {control-O} in that the person is asked to stop talking (perhaps because you are on the phone) but will be allowed to continue when you're ready to listen to him ---

as opposed to control-O, which has more of the meaning of "Shut up." Considered silly.

:Conway's Law: prov. The rule that the organization of the software and the organization of the software team will be congruent; originally stated as "If you have four groups working on a compiler, you'll get a 4-pass compiler".

This was originally promulgated by Melvin Conway, an early proto-hacker who wrote an assembler for the Burroughs 220 called SAVE. The name `SAVE' didn't stand for anything; it was just that you lost fewer card decks and listings because they all had SAVE

written on them.

:cookbook: [from amateur electronics and radio] n. A book of small code segments that the reader can use to do various {magic}

things in programs. One current example is the `{PostScript}

Language Tutorial and Cookbook' by Adobe Systems, Inc (Addison-Wesley, ISBN 0-201-10179-3) which has recipes for things like wrapping text around arbitrary curves and making 3D fonts.

Cookbooks, slavishly followed, can lead one into {voodoo programming}, but are useful for hackers trying to {monkey up}

small programs in unknown languages. This is analogous to the role of phrasebooks in human languages.

:cooked mode: [UNIX] n. The normal character-input mode, with interrupts enabled and with erase, kill and other special-character interpretations done directly by the tty driver. Oppose {raw mode}, {rare mode}. This is techspeak under UNIX but jargon elsewhere; other operating systems often have similar mode distinctions, and the raw/rare/cooked way of describing them has spread widely along with the C language and other UNIX exports.

Most generally, `cooked mode' may refer to any mode of a system that does extensive preprocessing before presenting data to a program.

:cookie: n. A handle, transaction ID, or other token of agreement between cooperating programs. "I give him a packet, he gives me back a cookie." The claim check you get from a dry-cleaning shop is a perfect mundane example of a cookie; the only thing it's useful for is to relate a later transaction to this one (so you get the same clothes back). Compare {magic cookie}; see also {fortune cookie}.

:cookie bear: n. Syn. {cookie monster}.

:cookie file: n. A collection of {fortune cookie}s in a format that facilitates retrieval by a fortune program. There are several different ones in public distribution, and site admins often assemble their own from various sources including this lexicon.

:cookie monster: [from "Sesame Street"] n. Any of a family of early (1970s) hacks reported on {{TOPS-10}}, {{ITS}}, {{Multics}}, and elsewhere that would lock up either the victim's terminal (on a time-sharing machine) or the {{console}} (on a batch {mainframe}), repeatedly demanding "I WANT A COOKIE". The required responses ranged in complexity from "COOKIE" through "HAVE A COOKIE" and upward. See also {wabbit}.

:copious free time: [Apple; orig. fr. the intro to Tom Lehrer's song "It Makes A Fellow Proud To Be A Soldier"] n. 1. [used ironically to indicate the speaker's lack of the quantity in question] A mythical schedule slot for accomplishing tasks held to