The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] lisp challenge
Date: Fri, 16 Feb 2018 14:28:35 -0800	[thread overview]
Message-ID: <20180216222835.GC27574@mcvoy.com> (raw)
In-Reply-To: <20180216220524.3B9A4156E80B@mail.bitblocks.com>

On Fri, Feb 16, 2018 at 02:05:09PM -0800, Bakul Shah wrote:
> On Fri, 16 Feb 2018 13:01:14 -0800 Larry McVoy <lm at mcvoy.com> wrote:
> Larry McVoy writes:
> > So people have called me on the claim that lisp is not fast.  Here's a 
> > rebuttal.
> > 
> > Please write a clone of GNU grep in lisp to demonstrate that the claim
> > that lisp is slower that C is false.
> > 
> > Best of luck and I'll be super impressed if you can get even remotely
> > close without dropping into C or assembler.  If you do get close, I 
> > will with draw my claim, stand corrected, point future "lisp is slow"
> > people at the lisp-grep, and buy you dinner and/or drinks.
> 
> If you want to do more of an apples to apples comparison, you
> should pick a brand new problem not known to be solved in
> either C or Lisp so that both sides start at the same point!

Nope.  It's my challenge and it stands as I stated it.  People said
I was wrong when I said Lisp was perceived as slow.  I picked a 
perfectly reasonable example of a common problem (text processing),
gave a benchmark, gave a pointer to how the C program was made fast,
and asked for a lisp program that even comes close.

If that can't be done, then the claim that lisp is slow still stands.

When people said I was "putting inaccuracies into the archives" or
"perpetuating a myth" I wondered if I was wrong.  Nobody said "well,
yes, C is faster for systems stuff or this or that, but lisp is faster
in this domain".  They said that the claim that lisp is slow is not
true.

Just saying that lisp is not slow is not the same as demonstrating it.

I'm more than willing to be wrong, that's how I learn.  But the proof
here is to show up with a pure lisp grep that is fast as the C version.
I'm no lisp expert, not by any stretch, but I've never seen a lisp
program that out performed a well written C program.

The point was that lisp was/is perceived as a slow language.  Several
people said that's false, I'm just asking for them to demonstrate that
it is false by writing grep in lisp.  Who knows?  Maybe it can be done.


  reply	other threads:[~2018-02-16 22:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 21:01 Larry McVoy
2018-02-16 21:03 ` Larry McVoy
2018-02-16 22:05 ` Bakul Shah
2018-02-16 22:28   ` Larry McVoy [this message]
2018-02-16 22:53     ` Donald ODona
2018-02-16 23:01       ` Arthur Krewat
2018-02-16 22:56     ` Arthur Krewat
2018-02-16 23:02       ` Larry McVoy
2018-02-16 23:18       ` Toby Thain
2018-02-16 23:41         ` Larry McVoy
2018-02-16 23:49     ` Bakul Shah
2018-02-16 23:34 ` Andy Kosela
2018-02-16 23:44 Noel Chiappa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180216222835.GC27574@mcvoy.com \
    --to=lm@mcvoy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).