From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] lisp challenge
Date: Fri, 16 Feb 2018 14:05:09 -0800 [thread overview]
Message-ID: <20180216220524.3B9A4156E80B@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Fri, 16 Feb 2018 13:01:14 -0800." <20180216210114.GA27574@mcvoy.com>
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!
I do think that if you consider just the raw performance as
the sole metric, C will almost always win. After all it is
sort of a portable assembly language & you can compile
programs in most language to C. But in the real world many
other factors matter too. So to make the contest a bit more
fair, you should put a time limit on the effort.
next prev parent reply other threads:[~2018-02-16 22:05 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 [this message]
2018-02-16 22:28 ` Larry McVoy
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=20180216220524.3B9A4156E80B@mail.bitblocks.com \
--to=bakul@bitblocks.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).