unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: jyavner@member.fsf.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: "Misunderstanding of the lambda calculus"
Date: Wed, 01 Feb 2006 09:52:45 +0100	[thread overview]
Message-ID: <85hd7jsboi.fsf@lola.goethe.zz> (raw)
In-Reply-To: <Pine.LNX.3.96.1060201074710.551B-100000@acm.acm> (Alan Mackenzie's message of "Wed, 1 Feb 2006 08:12:46 +0000 (GMT)")

Alan Mackenzie <acm@muc.de> writes:

> Hi, David!
>
> On Tue, 31 Jan 2006, David Kastrup wrote:
>
>>"Richard M. Stallman" <rms@gnu.org> writes:
>
>>>     As you can see, practically all meanings involve surviving into
>>>     the present time.  So I stand by my point that "archaic" and
>>>     "dead" are not synonymous.
>
>>> Archaic does not imply "dead", but it does imply "not very much
>>> alive".  Anyway, the relevant point is "archaic" is a smear term.
>
>>"Archaic life forms" are those that have survived basically unchanged
>>for millions of years, that were so well-adapted to their ecological
>>niche that natural selection has not weeded them out or made them
>>undergo significant changes.  That's not really a "smear term".
>
> David, "archaic" _is_ a smear term in this context.

Proper smear terms would be "obsolescent", "obsolete", "retarded".
While I agree that "archaic" might be intended to smear here, it is
applied because of a lack of a significant reason.  It is similar to
the use of "liberal" in U.S. circles.

>>It does imply "strange to behold as holding its own in modern times
>>where lots of things have changed utterly in comparison".  But that
>>is indeed something that I don't consider an unfitting sentiment
>>when confronted with Emacs.  Though TeX fits the bill even better.
>
> Of course, the real truth is that it's taken other commonly used
> languages (like C++, Java, ....) decades to catch up with Lisp.  :-)

Not at all.  There is no catching up here that I can see: completely
different ecological niches.  Humans didn't evolve due to playing
catch up with duck-billed platypuses.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2006-02-01  8:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1F3FdP-0002xe-OW@monty-python.gnu.org>
2006-01-29 17:51 ` "Misunderstanding of the lambda calculus" Jonathan Yavner
2006-01-29 18:32   ` David Kastrup
2006-01-30 18:46     ` Richard M. Stallman
2006-01-30 19:28       ` David Kastrup
2006-01-31 18:03         ` Richard M. Stallman
2006-01-31 19:47           ` Kevin Rodgers
2006-01-31 20:09           ` Stefan Monnier
2006-02-01 19:38             ` Richard M. Stallman
2006-01-31 21:57           ` David Kastrup
2006-02-01  8:12             ` Alan Mackenzie
2006-02-01  8:52               ` David Kastrup [this message]
2006-02-01 10:40                 ` Miles Bader
2006-02-01 15:01                   ` Jonathan Yavner
2006-02-01 19:39             ` Richard M. Stallman
2006-01-29  5:42 Chong Yidong

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=85hd7jsboi.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jyavner@member.fsf.org \
    --cc=rms@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).