Second, you can send your bug reports to the site that I stole the snippet from:
No, the bug report goes to you, because you were the one who was too inept to cut-and-paste it correctly. The code on the web site works; the code in your post doesn't.
By the way, your argument ("And any programming language that allows garbage like this deserves to be knocked") is inept too. There are intelligent arguments to be made against Perl, but this isn't one of them.
Code blocks like that don't really impress me. Anyone can write code, remove all white-space, use terse meaningless variable names and call it "l33t".
I don't think that's what I did when I wrote this code. I only took out the whitespace because I wanted to use the code as my usenet signature, and the Usenet etiquette limits signatures to four lines.
Here's a version of the same program that has the proper whitespace and variable and function names. If you take the time to look at it closely I think you're more likely to find it impressive.
(Here's a hint: the most important part of the program is the string ".URRUUxR". If you think you understand this program, but you don't understand why this string contains those particular characters, then you don't understand the program.)
Second, put all of your fucking points on a slide - don't make me click through 5 fucking html pages just so that I can read the contents of one
pathetic slide.
Hi. You may not be clear on the idea
of a conference presentation. In a conference presentation, a speaker, such as me, stands in front of the audience and shows the slides to
everyone at once while explaining the content
in detail and answering occasional questions.
These are slides from a conference presentation, which means that the speaker (that's me, remember) would be doing the clicking. The audience members (that's you) typically do not click the 5 fucking HTML pages. So the number of clicks is not normally a matter of concern for the audience.
I hope this clears up your misunderstanding.
According to the slide notes, there are 43 slides in that presentation, which I presume took 45 minutes. That means about 1 slide per minute - wow!
Actually it was a 22 minute talk. (Double wow!) Perhaps you might like to meditate on the difference between a complex technical talk (not this one) and a humorous nontechnical talk (this talk). Here's a hint: After I show the pictures of the happy baby or the unhappy Japanese lady, I don't need to leave them on the screen for five minutes for the audience to absorb the full import.
Before it starts he says "How many people have taken $OTHER_TUTORIAL_NAME I gave last year?".... to those who raise their hands he says
"Well, you should go find something else to do, because $THIS_TUTORIAL is the same as $OTHER_TUTORIAL, only the name has changed"
I'm really sorry you were inconvenienced. The tutorial description that I sent to O'Reilly in my proposal stated very clearly (and I quote):
Caution; This tutorial is substantially the same as last year's
"Advanced Programming Techniques" class. People who took that class
last year whould not take this one.
However, the O'Reilly folks, for whatever reason, omitted this from the brochure.
I was not sent the brochure for proofreading or correction beforehand. I did send them mail on
April 18 to ask them to add the warning back to the description on the web site. I believe this was the first day that the brochure was available online.
I will cheerfully own up to many faults, including that of being a condescending, obnoxious elitist asshole.
But this particular problem
really wasn't my fault. I understand how annoying it must have been to have to switch classes,
but I don't think there was any way I could have handled this better.
Again, I'm sorry you were inconvenienced.
If there was something I could have done differently that I haven't thought of, I
hope you'll send me email to tell me what it could have been.
> The point is a Perl users' group isn't > appropriate to talk about strong typing and or ML.
That's rather presumptuous! It is not for you
to say what is appropriate for a Perl users' group and what is not appropriate. It is up to
the memebers of the group. If they want to
hear a talk about cultivation of mangel-wurzels,
that is none of your business.
The Philadelphia Perl Mongers invited
me to give a talk about strong typing.
If they had not want wanted to hear a talk about that,
they would not have invited me to give one.
> The guy goes to a Perl group and talks to >them about the wonders of ML, and is amazed
> that people get defensive about Perl.
You seem to think that a person at Perl User Group
must automatically become defensive just because
someone else is talking about the benefits of
a lanaguge other than Perl.
That is exactly the big problem with the
way we discuss programming languages.
You don't have to get defensive
when someone shows
a new way to solve a problem,
just because it is different
from the way that you know.
> Why not discuss ML at the ML users' group?
Why not indeed? I guess you should take that up with
the Philadelphia Perl Mongers, who invited
me to speak to them about strong typing.
What their reasons are, I cannot say.
I wasn't advocating against advocacy.
I was pointing out specific problems with
the way we do it: primarily that it leads to
patterns of discourse which inhibit real communication,
and also that it's ineffective.
> advocate for an antidote to ignorance
Nice words from the guy who misrepresented my point without even reading the entire article.
Slashdot Mirror
First post!!!!
By the way, your argument ("And any programming language that allows garbage like this deserves to be knocked") is inept too. There are intelligent arguments to be made against Perl, but this isn't one of them.
Tom St. Denis said:
//, ".URRUUxR";
/^[P.]/ && close $_
/^r/ ? <$_> : 1 } %pipestate;
/\S/;
.
Code blocks like that don't really impress me.
Anyone can write code, remove all white-space,
use terse meaningless variable names and call
it "l33t".
I don't think that's what I did when I wrote this code. I only took out the whitespace because I wanted to use the code as my usenet signature, and the Usenet etiquette limits signatures to four lines.
Here's a version of the same program that has the proper whitespace and variable and function names.
If you take the time to look at it closely I think you're more likely to find it impressive.
(Here's a hint: the most important part of the program is the string ".URRUUxR". If you think you understand this program, but you don't understand why this string contains those particular characters, then you don't understand the program.)
@STATE = split
@data = split//,"\nrekcah xinU / lreP rehtona tsuJ";
sub make_pipe_and_fork {
@pipestate{"r$fhno", "u$fhno"}=(P,P);
pipe "r$fhno", "u$fhno";
++$fhno;
($pid *= 2) += $is_child = !fork();
map {
$STATE=$STATE[$is_child | ord($pipestate{$_}) & 6];
$pipestate{$_} = (/^$STATE/i ? $STATE : close $_);
} keys %pipestate
}
make_pipe_and_fork;
make_pipe_and_fork;
make_pipe_and_fork;
make_pipe_and_fork;
make_pipe_and_fork;
map {
$pipestate{$_} =~
} %pipestate;
wait until $?;
map {
$_ = $data[$pid];
sleep rand(2) if
print
For hints and explanataions, see my web site at
http://perl.plover.com/obfuscated/
My site was not slashdotted.
I was moving house and changing ISPs.
If anyone would like to mirror this, please drop me a note and I'll send the stuff over.
Second, put all of your fucking points on a slide - don't make me click through 5 fucking html pages just so that I can read the contents of one pathetic slide.
Hi. You may not be clear on the idea of a conference presentation. In a conference presentation, a speaker, such as me, stands in front of the audience and shows the slides to everyone at once while explaining the content in detail and answering occasional questions.
These are slides from a conference presentation, which means that the speaker (that's me, remember) would be doing the clicking. The audience members (that's you) typically do not click the 5 fucking HTML pages. So the number of clicks is not normally a matter of concern for the audience.
I hope this clears up your misunderstanding.
According to the slide notes, there are 43 slides in that presentation, which I presume took 45 minutes. That means about 1 slide per minute - wow!
Actually it was a 22 minute talk. (Double wow!) Perhaps you might like to meditate on the difference between a complex technical talk (not this one) and a humorous nontechnical talk (this talk). Here's a hint: After I show the pictures of the happy baby or the unhappy Japanese lady, I don't need to leave them on the screen for five minutes for the audience to absorb the full import.
Hope this helps.
Before it starts he says "How many people have taken $OTHER_TUTORIAL_NAME I gave last year?" .... to those who raise their hands he says
"Well, you should go find something else to do, because $THIS_TUTORIAL is the same as $OTHER_TUTORIAL, only the name has changed"
I'm really sorry you were inconvenienced. The tutorial description that I sent to O'Reilly in my proposal stated very clearly (and I quote):
However, the O'Reilly folks, for whatever reason, omitted this from the brochure. I was not sent the brochure for proofreading or correction beforehand. I did send them mail on April 18 to ask them to add the warning back to the description on the web site. I believe this was the first day that the brochure was available online.
I will cheerfully own up to many faults, including that of being a condescending, obnoxious elitist asshole. But this particular problem really wasn't my fault. I understand how annoying it must have been to have to switch classes, but I don't think there was any way I could have handled this better.
Again, I'm sorry you were inconvenienced. If there was something I could have done differently that I haven't thought of, I hope you'll send me email to tell me what it could have been.
Best regards,
Mark DominusThe notes
The Philadelphia Perl Mongers invited me to give a talk about strong typing. If they had not want wanted to hear a talk about that, they would not have invited me to give one.
That is exactly the big problem with the way we discuss programming languages.
You don't have to get defensive when someone shows a new way to solve a problem, just because it is different from the way that you know.
Why not indeed? I guess you should take that up with the Philadelphia Perl Mongers, who invited me to speak to them about strong typing. What their reasons are, I cannot say.Your program didn't work for me.
I wonder why not?
Oh, it's because in Python, whitespace is
significant.
And now that it's gone, it's awfully hard to put it back because there's no other syntax indicating the block structure.
Too bad about that, huh?