Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion can lisp do what perl does easily?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Kragen Sitaker  
View profile  
 More options Mar 29 2000, 3:00 am
Newsgroups: comp.lang.lisp
From: kra...@dnaco.net (Kragen Sitaker)
Date: 2000/03/29
Subject: Re: can lisp do what perl does easily?
Very interesting article, Erik.  As always :)

In article <3163193555464...@naggum.no>, Erik Naggum  <e...@naggum.no> wrote:

>    also, very much unlike any other language I
>  have ever studied, perl has failed to stick to memory, a phenomenon that
>  has actually puzzled me, but I guess there are some things that are so
>  gross you just have to forget, or it'll destroy something with you.  perl
>  is the first such thing I have known.

Perl is so large and complex that it makes Common Lisp, COBOL, and C++
look small and simple by comparison.  Large and complex things are hard
to memorize.

I just refer to the manual a lot.

>  it's not that perl programmers are idiots, it's that the language rewards
>  idiotic behavior in a way that no other language or tool has ever done,
>  and on top of it, it punishes conscientiousness and quality craftsmanship
>  -- put simply: you can commit any dirty hack in a few minutes in perl,
>  but you can't write an elegant, maintainabale program that becomes an
>  asset to both you and your employer;

CGI.pm is a counterexample, IMHO.

Can you give some concrete examples of how Perl rewards idiotic
behavior and punishes conscientiousness?  I must be so brainwashed that
it's not obvious to me.

>  you can make something work, but you can't really figure out its
>  complete set of failure modes and conditions of failure.  (how do
>  you tell when a regexp has a false positive match?)

This is a serious criticism, and one that I agree with to some extent.
I tend to think the power of Perl's hard-to-predict features outweigh
their difficulty of prediction.

I'd be interested to see some examples of short Perl snippets that had
subtle failure modes and a shorter (or quicker to read and write)
Common Lisp snippet that performed the same function, without the
subtle failure modes.  I can think of a few --- there's one in perldoc
-f open.  :)

>  and once you start down this path [of stupid data formats], every
>  move forward is a lot cheaper than any actual improvements to the
>  system that would _obviate_ the need for more glue code.  however,
>  if you never start down this path, you have a chance of making
>  relevant and important changes.

There are a lot of systems I talk to that have stupid data formats, and
it doesn't matter how much I want to fix them; I can't.

Perl is better than anything else I know at handling stupid data
formats reliably and effortlessly.

>  few perl programmers are actually good at anything but getting perl
>  to solve their _immediate_ problems, so you have an incredible
>  advantage if you're a good Lisper.

I think you mean "are not actually good", not "are actually good".

Most Perl programmers are not skilled programmers.  Perl makes it
possible for them to do things they couldn't have done by hand, and
makes it possible for them to do things more reliably and quickly than
they could have done them by hand.  It does not turn them into
competent programmers.

Getting something useful out of Lisp requires that you be at least a
minimally competent programmer, so there are few Lisp programmers who
are not at least minimally competent.
--
<kra...@pobox.com>       Kragen Sitaker     <http://www.pobox.com/~kragen/>
The Internet stock bubble didn't burst on 1999-11-08.  Hurrah!
<URL:http://www.pobox.com/~kragen/bubble.html>
The power didn't go out on 2000-01-01 either.  :)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.