From: mutiny.mutiny@india.com (Donald ODona)
Subject: [TUHS] lisp challenge
Date: Fri, 16 Feb 2018 22:53:49 +0000 (UTC) [thread overview]
Message-ID: <903259418.38276.1518821629141.JavaMail.tomcat@india-live-be02> (raw)
In-Reply-To: <20180216222835.GC27574@mcvoy.com>
I definitely agree with your words. Furthermore I point to the fact
that lisp is totally different to any other language, the archaic
algol, cobol and fortran languages included. Therefore one makes
automatically mistakes after longer periods of intensive
lisp coding and vice versa, despite the fact that the lisp approach
basically is very simple, not to say oversimplified. Anyhow there
aren't many lispers anymore. In business lisp plays no role at all.
Its a pet of so backward oriented academicians.
At 16 Feb 2018 22:29:33 +0000 (+00:00) from Larry McVoy <lm at mcvoy.com>:
> 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.
>
>...
next prev parent reply other threads:[~2018-02-16 22:53 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
2018-02-16 22:53 ` Donald ODona [this message]
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=903259418.38276.1518821629141.JavaMail.tomcat@india-live-be02 \
--to=mutiny.mutiny@india.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).