From: Ian Grant <ian.a.n.grant@googlemail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: A comprehensible introduction to Ian Grant's ideas
Date: Sat, 4 Oct 2014 21:57:33 -0400 [thread overview]
Message-ID: <CAKFjmdzD4YUQzz3S8sz8+s_H9a-HOayhcdk0x_5wRoFk2v_rCw@mail.gmail.com> (raw)
In-Reply-To: <87fvf4fl9p.fsf@netris.org>
On Sat, Oct 4, 2014 at 1:37 AM, Mark H Weaver <mhw@netris.org> wrote:
> Ian, you are a _terrible_ communicator. IMO, your biggest problems are:
>
> 1. You present your ideas in a far too abstract way, making it hard for
> those of us who haven't already been long acquainted with your ideas
> to begin to understand them.
This is correct. They are extremely abstract, because they are nothing
more than the true essence of the idea of abstraction itself.
Abstraction is the nature of language, and so language
implementations, if they are to be useful, must be entirely abstract.
There must be no trace of any particular concrete representation
whatsoever, because it is through identifying the language with a
particular concrete implementation that the abstraction 'leaks
information.'
> 2. You write far too much, making it hard for us to find the few
> writings of yours that might be able to get through our thick skulls.
I have written a lot, and it is incoherent. This is because I am
having to counter
objections from people who have not understood what I wrote. These
objections have been many, and of course they are all incoherent!
> 3. You insult us, making us predisposed to want to dismiss you.
If you look, and try to find a counter-example in anything I have
written, you will find that I have not insulted anyone. I hope though,
that I have made some people feel like complete idiots. That was
definitely my intention. The problem is that,complete idiots being
what they are, they invariably think they've been insulted when they
are made to feel like this. :-)
> However, I found a blog post of yours that I believe is a relatively
> good introduction to your ideas. I suspect this is because it is a
> response to Paul Koning, who had the effect of keeping your thoughts
> organized, and less abstracted.
This is the contra-positive of what I have just argued: anyone who
takes the trouble to read and understand what I have written will find
they have this "magical effect" on me.
> For those who would like to try to understand Ian's ideas, I would
> recommend first reading this excellent interview with Edsger Dijkstra,
> which Ian cites in his post:
>
> http://www.cs.utexas.edu/users/EWD/misc/vanVlissingenInterview.html
>
> and then read Ian's response to Paul Koning:
>
> http://livelogic.blogspot.com/2014/09/the-free-fair-and-forged.html
I hope there will be many more posts like this, one for each
intelligent, coherent criticism I get of "my ideas."
Ian
prev parent reply other threads:[~2014-10-05 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 5:37 A comprehensible introduction to Ian Grant's ideas Mark H Weaver
2014-10-04 12:32 ` Taylan Ulrich Bayirli/Kammer
2014-10-05 1:57 ` Ian Grant [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKFjmdzD4YUQzz3S8sz8+s_H9a-HOayhcdk0x_5wRoFk2v_rCw@mail.gmail.com \
--to=ian.a.n.grant@googlemail.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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.
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).