From: Kurt B. Kaiser
Subject: [comp.lang.python] [Re: is c faster?] Lisp v. Python
Date: 
Message-ID: <m3n17av6ny.fsf@float.ne.mediaone.com>
Ahem!


From: Michael Hudson <···@python.net>
Newsgroups: comp.lang.python
Subject: Re: is c faster?

Chris Barker <············@home.net> writes:

> Alex Martelli wrote:
> > whatnot.  I think this is the kind of benefit one
> > might expect from a simpleminded 'compiler':-). 
> 
> That's why we need a not so simple minded compiler. I have a friend that
> keeps harping on the fact that LISP can be as fast as C and as dynamic
> as Python. Why can't Python do that?

IHMO: Money, and brains.  The people who developed the techniques for
optimizing lisp working for Symbolics et al. were very very smart, and
were paid to work on such things.  There's just not the money in the
Python industry.

Also, Common Lisp isn't as, or rather is differently dynamic to
Python.  For instance you can't redefine (any of the many spellings
of) equality in CL; if yow wanted to do that you'd be more likely to
shadow cl:= inside your package, and this has got to be easier to spot
at compile time.

Cheers,
M.

-- 
  I'm a keen cyclist and I stop at red lights.  Those who don't need
  hitting with a great big slapping machine.
                                           -- Colin Davidson, cam.misc
From: Michael Hudson
Subject: Re: [comp.lang.python] [Re: is c faster?] Lisp v. Python
Date: 
Message-ID: <m3vglyurd1.fsf@atrus.jesus.cam.ac.uk>
···@shore.net (Kurt B. Kaiser) writes:

> Ahem!

And your point is?

Cheers,
M.

> From: Michael Hudson <···@python.net>
> Newsgroups: comp.lang.python
> Subject: Re: is c faster?
> 
> Chris Barker <············@home.net> writes:
> 
> > Alex Martelli wrote:
> > > whatnot.  I think this is the kind of benefit one
> > > might expect from a simpleminded 'compiler':-). 
> > 
> > That's why we need a not so simple minded compiler. I have a friend that
> > keeps harping on the fact that LISP can be as fast as C and as dynamic
> > as Python. Why can't Python do that?
> 
> IHMO: Money, and brains.  The people who developed the techniques for
> optimizing lisp working for Symbolics et al. were very very smart, and
> were paid to work on such things.  There's just not the money in the
> Python industry.
> 
> Also, Common Lisp isn't as, or rather is differently dynamic to
> Python.  For instance you can't redefine (any of the many spellings
> of) equality in CL; if yow wanted to do that you'd be more likely to
> shadow cl:= inside your package, and this has got to be easier to spot
> at compile time.
> 
> Cheers,
> M.
> 
> -- 
>   I'm a keen cyclist and I stop at red lights.  Those who don't need
>   hitting with a great big slapping machine.
>                                            -- Colin Davidson, cam.misc

-- 
  For their next act, they'll no doubt be buying a firewall 
  running under NT, which makes about as much sense as 
  building a prison out of meringue.                     -- -:Tanuki:-
               -- http://home.xnet.com/~raven/Sysadmin/ASR.Quotes.html