"This file, jargon.txt, was maintained on MIT-AI for many years, before being published by Guy Steele and others as the Hacker's Dictionary. Many years after the original book went out of print, Eric Raymond picked it up, updated it and republished it as the New Hacker's Dictionary. Unfortunately, in the process, he essentially destroyed what held it together, in various ways: first, by changing its emphasis from Lisp-based to UNIX-based (blithely ignoring the distinctly anti-UNIX aspects of the LISP culture celebrated in the original); second, by watering down what was otherwise the fairly undiluted record of a single cultural group through this kind of mixing; and third, by adding in all sorts of terms which are "jargon" only in the sense that they're technical. This page, however, is pretty much the original, snarfed from MIT-AI around 1988." The -P convention: turning a word into a question by appending the syllable "P"; from the LISP convention of appending the letter "P" to denote a predicate (a Boolean-values function). The question should expect a yes/no answer, though it needn't. (See T and NIL.) At dinnertime: "Foodp?"
I'm old enough to have been active in this era, and to have sent messages on teletypes using the "P" suffix. But for us, it had nothing to do with LISP. Our machines weren't that cool.In fact, they were so lame that many of the printing terminals lacked a question mark character. The P was used as a substitute for a ? because it was the closest visual substitution. And naturally, most of our messages were one or two words for economy. "FOODP" would print correctly on machines that couldn't print "FOOD?" Not everyone had a fancy glass terminal, so you had to assume the worst case scenario, and use "P" in case someone was on paper.
On a related note, to make it easier to count spaces in indented code, we would use a "b" character with a slash through it. So the teletype was print b, then back up a space by sending ^H, and then put a / through it.
It looked terrible, but got the job done. It used up a lot of ink, but the bosses were watching paper use, not ink.
We used to even use this in speech sometimes, especially when funny (say, agreeing to share Hot and Sour soup at Mary's, for which the conversation above would work well).
Note the amusing pointlessness of p in this case since when speaking you'd pronounce a question anyway.
I wonder if there's a unicode for that.
AI:HUMOR;MITSAI JARGON (25.3 KB):
https://github.com/PDP-10/its/blob/master/doc/humor/mitsai.j...
AI:HUMOR;JARGON > (85.3 KB):
https://github.com/PDP-10/its/blob/master/doc/humor/jargon.6...
Also NASA jargon:
https://github.com/PDP-10/its/blob/master/doc/humor/nasa.jar...
Alice's PDP-10 is also a classic:
https://github.com/PDP-10/its/blob/master/doc/humor/alices.p...
There was all kinds of mean nasty ugly people there on the bench...
Chaosnet designers... Lisp hackers... TECO hackers. TECO hackers
right there on the bench with me! And the meanest one of them, the
hairiest TECO hacker of them all was coming over to me. And he was
mean and nasty and horrible and undocumented and all kinds of stuff.
And he sat down next to me and said:
[1:i\*^Yu14<q1&377.f"nir'q1/400.u1>^[[8
.-z(1702117120m81869946983m8w660873337m8w1466458484m8
)+z,.f^@fx\*[0:ft^]0^[w^\
And I said "I didn't get nothing, I had to rebuild the bittable in
queue six" and he said:
[1:i\*^Yu16<q1&77.+32iq1f"l#-1/100.#-1&7777777777.'"#/100.'u1r>6c^[[6
.(675041640067.m6w416300715765.m6w004445675045.m6
455445440046.m6w576200535144.m6w370000000000.m6),.fx\*[0:ft^]0^[w^\Reminds me, some fortunes on LAMBDA.TXT[1] seem to hint at the existence of an "Alice's LispM", seemingly a parody on the PDP-10 version, but a quick search for it doesn't seem to come up with much (I haven't looked very hard). Does anybody know anything about this?
Haven't heard the song for awhile.
Not only that, but the man's disgusting political and social views tarnished everything he touched.
This is such an interesting group dynamic where a work product of one group gets twisted by another group and claims ownership.
The embrace and extend method.
..........and mercilessly mock Eric Raymond for his pretensions. :D
2) after a while if person A takes this on, there will be a request to powerwash the gratuitous A’s edits and insertions off of it
3) if the purpose is to have it in pristine state and do no edits, it’s not like old versions have disappeared, just mirror them away
...this is starting to sound like a blockchain, isn't it.
I am glad Monty Python, at least, remains popular across old hackers and new.
‐ Dennis Ritchie
Actually surprised the American's weren't calling # "pound" then, but maybe that evilness showed up later. But whatever, it's never been a pound symbol in any country that uses pounds!
Another interesting fact about # is that in the late 90s or early 2000s, British Telecom tried to gaslight the British public into thinking that # was pronounced "octothorpe". Fortunately, everybody realised this was idiocy, and we all carried on calling it "hash" like we always had.
Hackers at large have moved away from Lisp despite Paul Graham and other evangelists, Linux ate Unix, and there have been several bright subcultures which have no meaningful presence in either edition of the Jargon file. Considering self-professed tribalism of the original authors, it’s hardly surprising.
Hackers also have moved away from academia at large, and 9-5 jobs at tech behemoths are more natural habitats for them, which also shaped the lingo. I mean, there’s a whole layer of slang usually pertinent to outsourcing agencies and to cubicle farms.
It would be interesting to have a compilation of jargon as it evolved through the 1990s and 2000s too.
There is the IBM Jargon File compiled by Mike Cowlishaw at the IBM UK Laboratories in Hursley. The most recent edition is from 1990. As you might expect, it has more about company traditions and workplace politics than the Guy Steele jargon file or its successors.
Newer cohorts don't always know the classics/perennials*, so the occasional thread is a good thing - but should we change the link to one of these?
https://www.dourish.com/goodies/jargon.html
http://jargon-file.org/archive/jargon-4.4.7.dos.txt
http://catb.org/jargon/html/index.html
* https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
The Jargon File - https://news.ycombinator.com/item?id=31574352 - May 2022 (1 comment)
The Jargon File - https://news.ycombinator.com/item?id=24658797 - Oct 2020 (4 comments)
The Jargon File - https://news.ycombinator.com/item?id=23331642 - May 2020 (2 comments)
The Jargon File - https://news.ycombinator.com/item?id=16424833 - Feb 2018 (1 comment)
Jargon File moved to github - https://news.ycombinator.com/item?id=6887903 - Dec 2013 (10 comments)
Jargon File moved to github - https://news.ycombinator.com/item?id=6884756 - Dec 2013 (3 comments)
The Original Hacker's Dictionary (1988) - https://news.ycombinator.com/item?id=5269170 - Feb 2013 (24 comments)
The Jargon File - https://news.ycombinator.com/item?id=1469112 - June 2010 (4 comments)
The Jargon File - https://news.ycombinator.com/item?id=1295076 - April 2010 (3 comments)
On ESR's continual changing of the Jargon File.. - https://news.ycombinator.com/item?id=239168 - July 2008 (1 comment)
The Jargon File - https://news.ycombinator.com/item?id=148423 - March 2008 (1 comment)
Big Room: http://www.hackersdictionary.com/html/entry/Big-Room.html
Bogo-Sort: http://www.hackersdictionary.com/html/entry/bogo-sort.html
Bug-For-Bug Compatible: http://www.hackersdictionary.com/html/entry/bug-for-bug-comp...
Fence-post Error: http://www.hackersdictionary.com/html/entry/fencepost-error....
Magic Smoke: http://www.hackersdictionary.com/html/entry/magic-smoke.html
One-Banana Problem http://www.hackersdictionary.com/html/entry/one-banana-probl...
Tail Recursion: http://www.hackersdictionary.com/html/entry/tail-recursion.h...
(The person who related this anecdote wasn't mocking him, it was just an example while talking about something else, using amusing examples that all of us would know. I don't remember Harrison, but I think I remember Robert Sheckley doing this, not that it matters).
Created a new account just to submit this? Welcome.