From: Martin Escardo <m.escardo@cs.bham.ac.uk>
To: categories <categories@mta.ca>, André <joyal.andre@uqam.ca>
Cc: Juergen Koslowski <koslowj@iti.cs.tu-bs.de>
Subject: Re: potential names
Date: Wed, 29 Sep 2010 05:45:50 +0100 [thread overview]
Message-ID: <E1P15ur-0001Zd-D4@mlist.mta.ca> (raw)
In-Reply-To: <E1P0kdv-00045H-OQ@mlist.mta.ca>
What about "dangerous" rather than "evil"? (I also dislike religious and
moral terminology for mathematics. I specially dislike the terminology
"morally true", which I often hear, although I like the concept.)
We frequently encounter dangerous situations in our mathematical paths,
no matter how hard we try to avoid them, but if we know what we are
doing it is ok.
In this discussion about "evilness", what is important is to know that
lack of invariance under isomorphisms is dangerous (and why this is so),
and that you must consciously know how to properly proceed if your
definition happens to be not invariant, be it for necessity, lack of a
better idea, or mere convenience.
MHE
Joyal wrote:
> Dear Juergen,
>
> You wrote:
>
>> Let me start by proposing "equi-unstable" and "precarious" as possible
>> replacements for "evil".
>
> I agree that we should explore various options.
> Strickly speaking, there is no need for a new terminology
> since "non-invariant" has been used in the past
> and it is working pretty well.
>
> Let me draw a list of potential names.
> I have added a few:
>
> non-invariant
> equi-unstable
> precarious
> unstable
> fragile
> private
>
> I invite everyone to contribute to the list.
>
> Best,
> AJ
>
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next prev parent reply other threads:[~2010-09-29 4:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 9:15 EVIL terminology Juergen Koslowski
[not found] ` <E1P0kdv-00045H-OQ@mlist.mta.ca>
2010-09-29 4:45 ` Martin Escardo [this message]
2010-10-01 14:40 ` potential names Todd Trimble
2010-10-02 17:43 ` Paul Taylor
2010-10-04 7:20 ` Vaughan Pratt
2010-10-03 14:27 ` Todd Trimble
2010-10-05 22:18 Fred E.J. Linton
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=E1P15ur-0001Zd-D4@mlist.mta.ca \
--to=m.escardo@cs.bham.ac.uk \
--cc=categories@mta.ca \
--cc=joyal.andre@uqam.ca \
--cc=koslowj@iti.cs.tu-bs.de \
/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).