From: Robert Uhl <ruhl@4dv.net>
Subject: Re: Around again, and docs lead role
Date: 04 May 2003 15:34:01 -0600 [thread overview]
Message-ID: <m33cju8khi.fsf@latakia.dyndns.org> (raw)
In-Reply-To: <Pine.BSF.4.51.0305031856310.29627@helena.whitefang.com>
Thamer Al-Harbash <tmh@whitefang.com> writes:
>
> > To be successful at that, it's useful to have a tutorial,
> > particularly when the language is as odd as a Lisp dialect can seem
> > as first. Those unfamiliar with Scheme who happen upon Guile are
> > likely to skip past, scared away by the parentheses and lack of a
> > thorough introduction.
>
> I propose placing a link from the guile page to an on-line copy of the
> Prentice Hall book which is reproduced there with the permission of
> the publisher.
It's my opinion (and I could be _quite_ wrong on this) that users don't
really care about the language/implementation distinction. They use
Perl; they use Python; they use Common Lisp; they use Guile. They don't
want to have to keep in mind `this is the core of the language, while
that is an implementation-specific add-on.' And really, they're kind of
right: just as there is a commonality between Common Lisp and Scheme, so
too there is a commonality between e.g. guile, gambit and SCM--but from
the user's point of view, they're not-quite-compatible & thus different.
What users want, I believe, is not an `introduction to Scheme,' but
rather an `introduction to guile.' The former tells them about a
language; the latter tells them how to solve their problems. I'm not
saying that viewpoint is necessarily right or wrong, but it's my
perception of what is in fact the case.
--
Robert Uhl <ruhl@4dv.net>
Christ is Risen! Truly He is Risen!
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-05-04 21:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 7:33 Around again, and docs lead role Neil Jerram
2003-04-26 10:19 ` Thamer Al-Harbash
2003-04-27 20:56 ` Neil Jerram
[not found] ` <3E92E1B40021F4D7@pop3.tiscalinet.es>
2003-04-27 21:01 ` Neil Jerram
[not found] ` <3E92E1B4002B0632@pop3.tiscalinet.es>
2003-04-30 22:47 ` Neil Jerram
[not found] ` <3EAFE4EC000D9733@pop1.tiscalinet.es>
2003-05-07 21:06 ` Doc organization (Re: Around again, and docs lead role) Neil Jerram
2003-05-08 16:21 ` Rob Browning
2003-05-08 17:50 ` rm
2003-05-08 22:47 ` Neil Jerram
2003-10-28 16:09 ` Thien-Thi Nguyen
2003-05-08 22:36 ` Neil Jerram
2003-05-09 2:23 ` Rob Browning
2003-05-09 17:46 ` David Van Horn
2003-05-10 11:32 ` Neil Jerram
2003-05-15 16:02 ` Rob Browning
2003-05-15 16:33 ` Paul Jarc
2003-05-09 11:52 ` Bill Schottstaedt
2003-05-13 23:01 ` Neil Jerram
2003-05-14 1:07 ` Viktor Pavlenko
2003-05-14 14:29 ` Bill Schottstaedt
2003-05-15 7:55 ` Mikael Djurfeldt
2003-05-17 3:02 ` Max Techter
2003-05-09 8:15 ` tomas
2003-05-10 12:01 ` Neil Jerram
2003-05-12 11:40 ` tomas
2003-05-03 4:40 ` Around again, and docs lead role Robert Uhl
2003-05-03 11:34 ` rm
2003-05-03 22:21 ` Robert Uhl
2003-05-03 23:15 ` Thamer Al-Harbash
2003-05-04 8:40 ` David Allouche
2003-05-04 21:34 ` Robert Uhl [this message]
2003-05-04 19:47 ` rm
2003-05-04 21:42 ` Robert Uhl
2003-05-04 23:38 ` Thien-Thi Nguyen
2003-05-07 22:52 ` Neil Jerram
2003-05-08 22:32 ` State of Docs [was] " rm
2003-05-08 23:11 ` Neil Jerram
2003-05-10 0:47 ` State of Docs Kevin Ryde
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=m33cju8khi.fsf@latakia.dyndns.org \
--to=ruhl@4dv.net \
/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).