«

jan V wrote:
> Did you know that some deranged people take sexual pleasure out of starting
> fires? Apparently some of the latest forest/bush fires in southern Europe
> were even started by firemen (with their pants down?).

I've only heard of people trying to extinguish fires with their pants
down. Oh well...

--
I believe in Karma. That means I can do bad things to people
all day long and I assume they deserve it.
Dogbert

In comp.lang.perl.misc Xah Lee <> wrote:
> The other class of jargon stupidity is from computing practitioners, of
> which the Unix/Perl community is exemplary. For example, the name Unix
> & Perl themselves are good examples of buzzing jargons. Unix is
> supposed to be opposed of Multics and hints on the offensive and
> tasteless term eunuchs.

Now that connexion is a product of a truely warped mind.

Axel

writes:

>In comp.lang.perl.misc Xah Lee <> wrote:
>> The other class of jargon stupidity is from computing practitioners, of
>> which the Unix/Perl community is exemplary. For example, the name Unix
>> & Perl themselves are good examples of buzzing jargons. Unix is
>> supposed to be opposed of Multics and hints on the offensive and
>> tasteless term eunuchs.
>
>Now that connexion is a product of a truely warped mind.

and one devoid of any trace of humour.

mkb.

the other canonical responses:

- killfile killfile killfile
- nothing to see here ... keep moving
- don't cross-post your replies, don't rile the perl users.

wrote:
> In comp.lang.perl.misc Xah Lee <> wrote:
>
>> The other class of jargon stupidity is from computing practitioners,
>> of which the Unix/Perl community is exemplary. For example, the name
>> Unix & Perl themselves are good examples of buzzing jargons. Unix is
>> supposed to be opposed of Multics and hints on the offensive and
>> tasteless term eunuchs.
>
> Now that connexion is a product of a truely warped mind.

If you really must feed the troll, please at least set follow-ups
to cut things back.

--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson

Xah Lee wrote:
> Jargons of Info Tech industry
>
> (A Love of Jargons)
>
> Xah Lee, 2002 Feb
>
> The jargon-soaked stupidity in computing field can be grouped into
> classes <SNIP> ... <SNIP> One flagrant example is Sun Microsystem's
> Java stuff <SNIP> ... <SNIP> ****ing stupid Java and **** Sun
> Microsystems. This is just one example of Jargon hodgepodge of one
> single commercial entity.
>
> The other class of jargon stupidity is from computing practitioners, of
> which the Unix/Perl community is exemplary <SNIP> ... <SNIP> These types of
> jargons exudes juvenile humor. Cheesiness and low-taste is their
> hall-mark.
>
> There is another class of jargon moronicity, which i find them most
> damaging to society, <SNIP> ... <SNIP> I think the reason for these, is that these
> massive body of average programers usually don't have much knowledge of
> significant mathematics, <SNIP> ... <SNIP> these people defining
> or hatching terms <SNIP> ... <SNIP> are often a result of sopho-morons
> trying to sound big.
>
<SNIP> ... <SNIP> Because most programers are
> sopho-morons who are less capable of clear thinking but nevertheless
> possess human vanity, <SNIP> ... <SNIP>
>
<SNIP> ... <SNIP> One can see that the term
> “closure” is quite vague in conveying its meaning. The term
> nevertheless is very popular among talkative programers and dense
> tutorials, precisely because it is vague and mysterious. These
> pseudo-wit living zombies, never thought for a moment that they are
> using a moronic term, <SNIP> ... <SNIP> (for an example of the
> fantastically stupid write-up on closure by the Perl folks <SNIP> ... <SNIP>
>
<SNIP> ... <SNIP>
>
<SNIP> ... <SNIP> (one may think from the above tree-diagram
> that Java the language has at least put clear distinction to interface
> and implementation, whereas in my opinion they are one fantastic ****
> up too, in many respects.)
>

I've extracted the preceding castigating snippets from Mr. Lee's Jargon
"thesis". ) When reciprocated upon his own posts; one could offer up
the proverb, "he who lives in glass houses should not throw stones."

His inflammatory rhetoric - light on facts, weak in application, and
generously peppered with self-aggrandizing insults - would probably
offend Jerry Springer by comparison.

Perhaps the "professor" should more carefully scrutinize himself before
attempting to castigate others, less he acquire the reputation of a
hypocrite, e.g. -
"are often a result of sopho-morons trying to sound big.";
"who are less capable of clear thinking but nevertheless possess
human vanity";
"These types of jargons exudes juvenile humor.";
"Cheesiness and low-taste is their hall-mark."

Elementary courses in Critical Reasoning, Topical Research, Grammar,
Creative Writing, and Technical Writing also seem warranted.

A little one on one time with a mental health practitioner probably
wouldn't hurt either. )

P.S. Until then, does anyones else deem it appropriate to give
"professor" Lee the nickname "Xah Lee Springer"?

Alex <> writes:
> Xah Lee wrote:
[SSSNNNIIIPPP!!!]
> I've extracted the preceding castigating snippets from Mr. Lee's
> Jargon "thesis".
[SSSNNNIIIPPP!!!]

*Please stop posting followups to this off-topic nonsense. Just
ignore it. Responding to spam is spam; responding to a troll gives
him exactly what he wants and annoys the heck out of the rest of us.

+-------------------+ .:\:\:/:/:.
| PLEASE DO NOT | :.:\:\:/:/:.:
| FEED THE TROLLS | :=.' - - '.=:
| | '=(\ 9 9 /)='
| Thank you, | ( (_) )
| Management | /`-vvv-'\
+-------------------+ / \
| | @@@ / /|,,,,,|\ \
| | @@@ /_// /^\ \\_\
@x@@x@ | | |/ WW( ( ) )WW
\||||/ | | \| __\,,\ /,,/__
\||/ | | | jgs (______Y______)
/\/\/\/\/\/\/\/\//\/\\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
================================================== ============

Followups redirected appropriately.

--
Keith Thompson (The_Other_Keith) kst- <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

Unix, RFC, and Line Truncation

[Note: unix tradition requires that a return be inserted at every 70
characters in email messages or so so that each line are less than 80
characters. Unixers made this as a requirement into an RFC document.]

Xah Lee, 20020511

This truncation of lines business is a hatred of mine, from email
formatting to formatting of program codes. I have been fighting with
the unix slew of morons about the line cut for years. The unix morons
are the number one excuse expert, that whenever in an argument they'll
mention some RFC “specifications”. (RFC = Really ****ing Common,
invented by mostly unix folks in the 70s.)

the unix morons, think that the world should truncate lines just like
their incompetent operating system silently truncate lines (and it
still DOES, folks! e.g. ps, tar, tcsh.) Around 1998 when i was using
Outlook Express or Eudora before that, i remember i can set lines to
not hard-wrap, and i did. Boy that always ****ed the unix blockheads.
In their diddly eyes and lousy email software, i'm breaking standards,
making things hard to read, and being a stupid ass. Their brain fail to
see what unix ways are not capable of. These guys are the same slew of
morons who cry in pain about how the web should not commercialize
(circa 1996), and email should be text only (anti-MIME, circa 1995),
and lynx is the best browser (circa 1995), and GUI is for sissys and
mouse is for pussies and Apple computer is for kids (circa 1987).

There is no reason for a paragraph encoding to be splattered with end
of line characters, nor the human labor expended. There is reason for
paragraphs to be displayed not too wide, and that is readability. What
the unixer could not get clear of is a distinction of concepts. Because
their fantastically hacked-up operating system operate by the principle
that lines should not be some 80 chars or else it will be truncated and
*silently* too, thus it became _necessarily_ their _habit_ and thought
that line truncation business is natural and a human duty. Unknown of
these setups, the unix geeks go by their presumption that all text
should be hard wrapped, as if parameters should be hard-coded.

I recall, two particular unix hotshots who bugged me about the line
truncations business is the Perl priest Tom Christiansen, who used to
reside over comp.lang.perl.*, and another unix jockey Chris Nandor, who
was a MacPerl proponent now the main maintainer. It is not a
coincidence that the people who go out of their way to complain about
any “format=flowed” or softwrapped or logically-formatted lines in
emails are always the unixers. The unix twits will start a flame war
over a petty formatting issue, because it's unix's training to bent
over pettiness, not to mention they are the ones who are retarded on
the issue of line truncation.

As i have alluded to above, there are serious problems with the
line-truncation ways of thinking. The gist is that it is a form of
physical formatting as opposed to logical. (think softwrap vs hardwrap,
parameter vs hard-code) Those who are familiar with the history or
reason for SGML and HTML should understand the problem. Many of you
familiar with drive of evolution of HTML from 1995 days to today's CSS
& XML should also understand the issue. We wish to encode information,
and be flexible about representation, not botching info into one
particular representation.

The harm done by the unixers to society is of a long lasting and
pervasive nature. First is the RFC, which serves as the mob's standard,
which requires that every emailer should be broken like unix, so that
unix can process them without problems. **** unix and **** unix geeks.
Secondly, it drains human labor. Right this second there are hundreds
of people pressing returns or fixing jagged lines unnecessarily.
Thinking and computer could have done that for us, if not for ****ing
stupid unix and its people. Thirdly, a generation of programs and
programer's times are wasted over tools that mutilate paragraphs into
pieces. (in emacs, there's fill-paragraph etc, and in BBEdit it's just
called “Hard Wrap”) Fourthly, physical formatting ultimately
multiply the process required on the data, as we can see in emails,
especially in combination with the stupid quote convention: “>”
(that's another unix invention.). But most importantly is that the
hard-liners instilled a bad notion, a confusion, that generated a
entire generation of utterly stupid programing languages and monkey
coders, starting with unix's C language.

As of 200506, the following two sites shows that
as late as 2001, unix tool tar (BSD) still truncate long file names.
• http://www.sourcekeg.co.uk/www.mysql.../mac-os-x.html
(local copy)
http://nrg.cs.usm.my/~tcwan/macosx_essentials.htm
(local copy)

--------------------
This post is archived at:
http://xahlee.org/UnixResource_dir/w...cate_line.html

Xah

∑ http://xahlee.org/

"Xah Lee" <> writes:
[the usual]

+-------------------+ .:\:\:/:/:.
| PLEASE DO NOT | :.:\:\:/:/:.:
| FEED THE TROLLS | :=.' - - '.=:
| | '=(\ 9 9 /)='
| Thank you, | ( (_) )
| Management | /`-vvv-'\
+-------------------+ / \
| | @@@ / /|,,,,,|\ \
| | @@@ /_// /^\ \\_\
@x@@x@ | | |/ WW( ( ) )WW
\||||/ | | \| __\,,\ /,,/__
\||/ | | | jgs (______Y______)
/\/\/\/\/\/\/\/\//\/\\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
================================================== ============

--
Keith Thompson (The_Other_Keith) kst- <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

> +-------------------+ .:\:\:/:/:.
> | PLEASE DO NOT | :.:\:\:/:/:.:
> | FEED THE TROLLS | :=.' - - '.=:
> | | '=(\ 9 9 /)='
> | Thank you, | ( (_) )
> | Management | /`-vvv-'\
> +-------------------+ / \
> | | @@@ / /|,,,,,|\ \
> | | @@@ /_// /^\ \\_\
> @x@@x@ | | |/ WW( ( ) )WW
> \||||/ | | \| __\,,\ /,,/__
> \||/ | | | jgs (______Y______)
> /\/\/\/\/\/\/\/\//\/\\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

Please don't use ASCII art... not everyone uses a fixed-width font for his
newsreader...............
(your picture looks all mangled here)