On Saturday, August 3, 2002, at 12:26 , Hytham Shehab wrote:
[..]
> wll, drieux,
> i understand what u mean if u r talking about using perl with cgi, but
> really i didn't understand much of ur replay.
> it would be very nice of you to explain why/how perl can be EVIL!?
[..]
fair question - but perchance a dangerously leading one.
While I personally hold that a solid understanding of medieval
heresy trials is a pre-requisite to software development. Pragmatically
I have come to accept that 'bodging' is the preferred art form that
one really needs to understand. { for those who do not have access to
the show 'junkyard wars' - may i recommend it. }
So prior to my arrival in the computer game my background was in
three general fields -
turko-ANZAC engineering - the fine art of fixing in the field
mechanical equipage with a screw driver, an adjustable spanner,
a large rock, and a hammer ( optional if your rock is large enough. )
{ the naval equivolent is 'jury rigging' }
field medicine - did you know that many things can be pressed into
service as medical devices when one notices that one does not
have what the manual requires. some social skills are required
if you plan to sterilize sutures with vanilla extract, if it
is the only thing in camp with a 14% alcohol content, as the
cook may have been planning to 'cook' with it...
free marketeering - formerly known as 'the black market' prior to the
systemic upgrade to the 'deregulation of marketting' in which one
focuses on being 'customer-centric' irregardless of any indigenous
legal complications... { this includes the sub-specialty of
Information Acquisition and Analysis - sometimes known as spying,
blackmailing, insider trading - but clearly a prototype for the
whole 'information management solution' space .... }
While it is not expressly clear to me that the inner kabal of the
perl klique comes from this refined background, the fact that perl
is so clearly the tool of choice to 'function' in this space gives
me pause to worry about the authors and the klique, and their deep
seated unresolved childhood issues.
Somewhere in 90/91 while doing benchmarking between perl and a
variety of other coding solutions - it was clear to me that it was
not going to be easy to validate the matrix of marketting spiel about
whether perl actually 'simplified' the process of scripting, in lieu
of the traditional sed/awk/sh "unix power tools" - and it became clear
to me that be that as it may, perl's core utility was as a unifying
platform given the simple premise:
"management remains unclear on their goals
and the RealCoders[tm] are delivering to that standard."
So rather than having to haul around Tk/Tcl et al, one could
simply hack it in perl/Tk and wander on... What some would call
'sed line noise' was "tolerable" as 'perl regular expression parsing'
since at least the reader could read perl - and/or hope to work out
what it was that the RegEx was suppose to be doing...
Where you and I clearly disagree is that at times it is just simpler
to hack out a basic CGI script in perl, in lieu of doing it right and
coding up the full on 'c' code as an apache module and/or the correct
implmentation as a tomcat servlet or a visual basic implementation
for IIS....
So what starts out as a simple set of 'work arounds' becomes a
systemic failure and obsessive compulsive disorder. At which point
one becomes 'the perl guy' - irregardless of one's original gender -
and finds that one has to start managing the information about which
releases of perl are now default on what OS's - as well as the ever
meandering stack of stuff IN the CPAN, and sourceforge and ....
Which leads to the need to start managing the 'upgrade' path from
what ever it was the vendor did or did not supply with their 'tape'
{which is now probably a CD} so that one can maintain having the
common platform across all platforms. Which is not as much a problem
to the sorts who only have one or two OS's or derivations - and so
they all look the same - but gets really annoying as you find that
your code has to work on both major derivations of *unix - Sys V
and BSD - as well as WIN32::* and ...
Why? Because slowly but surely you have a body of code that rests upon
various facets of the recent release of perl and the ever growing
addiction to modules you downloaded from the CPAN in lieu of writing
them yourself....
Suddenly all the excuses you used for 'hacking it in perl' are no
longer working for you and you're back to having to do basic design
and analysis of the problem to effectively implement maintainable
code so that you don't have to come back here and re-hack it all again...
Perl was suppose to be a simpler 'scripting' language - not a full
on coding environment with all sorts of technical stuff....
But it's the little stuff along the way that you need to watch out
for in all of this! First it's that simple stack of maybe five or
six rules about how to write portable perl code that is readable. And
you notice that suddenly you can not recall the french security appart,
but feel ok, because you can still walk the tree of the KGB/GRU and
the distinctions of MI5/MI6 et al - so you think it's ok. Then about
the time you accidentally have subclassed someone else's project to
get your widgetFest to fly as you need it - BANG! There goes all of
your memories on how to differenciate between East German Headstamps
on M1943 7.62x39mm rounds and the rest of the makers of AK rounds.
By the time you have ginned up your first few major perl modules with
h2xs, because it's simpler than trying to bit twiddle perl libraries,
you notice that you've totally misplaced your memory space for where
the safety is, and how to field strip a whole collection of weapons
that are popular and available!
Next thing you know, you're having a coffee break and interleaving
tales about 'the good old days' with your opposite number from the
GRU, and why the correct solution to the problem is do-able in Perl....
Or worse yet - finding out that they were pulling off the scam about
"mother, I'm off to study my ham radio operating at the Komsomol"
when what they really were doing was going to meet some boy they had
met and thought was cute....
I mean Mien Gott Im Himmel!!!!
Do YOU want Perl to Eat Up Your Cultural Heritage????
Think of the Children!!!!
Innocent Children who are every year being sucked into the
horrid maw of perl - and the challenge to do that in a few
lines of perl code....
Just SAY NO!!!!
Perl is EVIL!!!!
ciao
drieux
---
but I could be over-reacting to all of this....
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]