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

in EMACS and a few mailers), the use of leading>' or > ' became standard, perhaps owing to its use ined(1)' to display tabs (alternatively, it may derive from the >' that some early UNIX mailers used to quote lines starting with "From" in text, so they wouldn't look like the beginnings of new message headers). Inclusions within inclusions keep their>' leaders, so the `nesting level' of a quotation is visually apparent.

A few other idiosyncratic quoting styles survive because they are automatically generated. One particularly ugly one looks like this: / Written hh:mm pm Mmm dd, yyyy by user@site in /

/* ---------- "Article subject, chopped to 35 ch" ---------- */ <quoted text> /* End of text from local:group */

It is generated by an elderly, variant news-reading system called `notesfiles'. The overall trend, however, is definitely away from such verbosity.

The practice of including text from the parent article when posting a followup helped solve what had been a major nuisance on USENET: the fact that articles do not arrive at different sites in the same order.

Careless posters used to post articles that would begin with, or even consist entirely of, "No, that's wrong" or "I agree" or the like. It was hard to see who was responding to what. Consequently, around 1984, new news-posting software evolved a facility to automatically include the text of a previous article, marked with "> " or whatever the poster chose. The poster was expected to delete all but the relevant lines.

The result has been that, now, careless posters post articles containing the entire text of a preceding article, followed only by "No, that's wrong" or "I agree".

Many people feel that this cure is worse than the original disease, and there soon appeared newsreader software designed to let the reader skip over included text if desired. Today, some posting software rejects articles containing too high a proportion of lines beginning with `>' --

but this too has led to undesirable workarounds, such as the deliberate inclusion of zero-content filler lines which aren't quoted and thus pull the message below the rejection threshold.

Because the default mailers supplied with UNIX and other operating systems haven't evolved as quickly as human usage, the older conventions using a leading TAB or three or four spaces are still alive; however, >-inclusion is now clearly the prevalent form in both netnews and mail.

In 1991 practice is still evolving, and disputes over the `correct'

inclusion style occasionally lead to {holy wars}. One variant style reported uses the citation character |' in place of>' for extended quotations where original variations in indentation are being retained.

One also sees different styles of quoting a number of authors in the same message: one (deprecated because it loses information) uses a leader of > ' for everyone, another (the most common) is> > > > ', `>

', etc. (or >>>> ',>>> ', etc., depending on line length and nesting depth) reflecting the original order of messages, and yet another is to use a different citation leader for each author, say > ',: ', | ',} ' (preserving nesting so that the inclusion order of messages is still apparent, or tagging the inclusions with authors'

names). Yet another style is to use each poster's initials (or login name) as a citation leader for that poster. Occasionally one sees a `#

' leader used for quotations from authoritative sources such as standards documents; the intended allusion is to the root prompt (the special UNIX command prompt issued when one is running as the privileged super-user).

Finally, it is worth mentioning that many studies of on-line communication have shown that electronic links have a de-inhibiting effect on people. Deprived of the body-language cues through which emotional state is expressed, people tend to forget everything about other parties except what is presented over that ASCII link. This has both good and bad effects. The good one is that it encourages honesty and tends to break down hierarchical authority relationships; the bad is that it may encourage depersonalization and gratuitous rudeness.

Perhaps in response to this, experienced netters often display a sort of conscious formal politesse in their writing that has passed out of fashion in other spoken and written media (for example, the phrase "Well said, sir!" is not uncommon).

Many introverted hackers who are next to inarticulate in person communicate with considerable fluency over the net, perhaps precisely because they can forget on an unconscious level that they are dealing with people and thus don't feel stressed and anxious as they would face to face.

Though it is considered gauche to publicly criticize posters for poor spelling or grammar, the network places a premium on literacy and clarity of expression. It may well be that future historians of literature will see in it a revival of the great tradition of personal letters as art.

:Hacker Speech Style:

=====================

Hackish speech generally features extremely precise diction, careful word choice, a relatively large working vocabulary, and relatively little use of contractions or street slang. Dry humor, irony, puns, and a mildly flippant attitude are highly valued --- but an underlying seriousness and intelligence are essential. One should use just enough jargon to communicate precisely and identify oneself as a member of the culture; overuse of jargon or a breathless, excessively gung-ho attitude is considered tacky and the mark of a loser.

This speech style is a variety of the precisionist English normally spoken by scientists, design engineers, and academics in technical fields. In contrast with the methods of jargon construction, it is fairly constant throughout hackerdom.

It has been observed that many hackers are confused by negative questions --- or, at least, that the people to whom they are talking are often confused by the sense of their answers. The problem is that they have done so much programming that distinguishes between if (going) {

and

if (!going) {

that when they parse the question "Aren't you going?" it seems to be asking the opposite question from "Are you going?", and so merits an answer in the opposite sense. This confuses English-speaking non-hackers because they were taught to answer as though the negative part weren't there. In some other languages (including Russian, Chinese, and Japanese) the hackish interpretation is standard and the problem wouldn't arise. Hackers often find themselves wishing for a word like French si' or Germandoch' with which one could unambiguously answer `yes' to a negative question.

For similar reasons, English-speaking hackers almost never use double negatives, even if they live in a region where colloquial usage allows them. The thought of uttering something that logically ought to be an affirmative knowing it will be misparsed as a negative tends to disturb them.

Here's a related quirk. A non-hacker who is indelicate enough to ask a question like "So, are you working on finding that bug now

or leaving it until later?" is likely to get the perfectly correct answer "Yes!" (that is, "Yes, I'm doing it either now or later, and you didn't ask which!").

:International Style:

=====================

Although the Jargon File remains primarily a lexicon of hacker usage in American English, we have made some effort to get input from abroad.

Though the hacker-speak of other languages often uses translations of jargon from English (often as transmitted to them by earlier Jargon File versions!), the local variations are interesting, and knowledge of them may be of some use to travelling hackers.

There are some references herein to `Commonwealth English'. These are intended to describe some variations in hacker usage as reported in the English spoken in Great Britain and the Commonwealth (Canada, Australia, India, etc. --- though Canada is heavily influenced by American usage).

There is also an entry on {{Commonwealth Hackish}} reporting some general phonetic and vocabulary differences from U.S. hackish.

Hackers in Western Europe and (especially) Scandinavia are reported to often use a mixture of English and their native languages for technical conversation. Occasionally they develop idioms in their English usage that are influenced by their native-language styles. Some of these are reported here.

A few notes on hackish usages in Russian have been added where they are parallel with English idioms and thus comprehensible to English-speakers.

:How to Use the Lexicon:

:Pronunciation Guide:

=====================

Pronunciation keys are provided in the jargon listings for all entries that are neither dictionary words pronounced as in standard English nor obvious compounds thereof. Slashes bracket phonetic pronunciations, which are to be interpreted using the following conventions: 1. Syllables are hyphen-separated, except that an accent or back-accent follows each accented syllable (the back-accent marks a secondary accent in some words of four or more syllables).

Consonants are pronounced as in American English. The letter g' is always hard (as in "got" rather than "giant");ch' is soft ("church" rather than "chemist"). The letter j' is the sound that occurs twice in "judge". The letters' is always as in "pass", never a z sound. The digraph `kh' is the guttural of "loch" or "l'chaim".

Uppercase letters are pronounced as their English letter names; thus (for example) /H-L-L/ is equivalent to /aitch el el/. /Z/ may be pronounced /zee/ or /zed/ depending on your local dialect.

Vowels are represented as follows:

a

back, that

ar

far, mark

aw

flaw, caught

ay

bake, rain

e

less, men

ee

easy, ski

eir

their, software

i

trip, hit

i:

life, sky

o

father, palm

oh

flow, sew

oo

loot, through

or

more, door

ow

out, how

oy

boy, coin

uh

but, some

u

put, foot

y

yet, young

yoo

few, chew

[y]oo

/oo/ with optional fronting as in `news' (/nooz/ or /nyooz/) A /*/ is used for the `schwa' sound of unstressed or occluded vowels (the one that is often written with an upside-down `e'). The schwa vowel is omitted in syllables containing vocalic r, l, m or n; that is, `kitten' and `color' would be rendered /kit'n/ and /kuhl'r/, not /kit'*n/ and /kuhl'*r/.

Entries with a pronunciation of `//' are written-only usages. (No, UNIX

weenies, this does not mean `pronounce like previous pronunciation'!) :Other Lexicon Conventions:

===========================

Entries are sorted in case-blind ASCII collation order (rather than the letter-by-letter order ignoring interword spacing common in mainstream dictionaries), except that all entries beginning with nonalphabetic characters are sorted after Z. The case-blindness is a feature, not a bug.

The beginning of each entry is marked by a colon (`:') at the left margin. This convention helps out tools like hypertext browsers that benefit from knowing where entry boundaries are, but aren't as context-sensitive as humans.

In pure ASCII renderings of the Jargon File, you will see {} used to bracket