From: Ivan Raikov <ivan.g.raikov@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: John Cowan <cowan@ccil.org>,
scheme-reports-wg1@googlegroups.com,
scheme-reports-wg2@googlegroups.com,
chicken chicken <chicken-users@nongnu.org>,
chibi-scheme@googlegroups.com, gambit-list@iro.umontreal.ca,
guile-user <guile-user@gnu.org>,
srfi-160@srfi.schemers.org
Subject: Re: Tangerine Edition penultimate report: how I voted, how you're voting
Date: Fri, 18 Jan 2019 12:20:28 -0800 [thread overview]
Message-ID: <CADM5OqP-jNjhJpbAmS7y8ygjtXY=HGc2Dx-qZyee6o0yB+zquA@mail.gmail.com> (raw)
In-Reply-To: <00545ca8-81d6-d4c5-5acc-142c87457692@bothner.com>
I thought the Great Compromise of R7RS was to have specifications for
both a small and a large language, so that everyone is happy (or at
least equally mad :-)) .
Isn't the difference with R6RS that R7RS-large draws extensively on
SRFIs which are indeed attempts to codify existing practices?
On Thu, Jan 17, 2019 at 5:15 PM Per Bothner <per@bothner.com> wrote:
>
> On 1/16/19 6:27 AM, John Cowan wrote:
> > So what is happening is that people are voting for more rather than less, as with the Red Edition. This encourages me that I'm going in a sensible direction with the large language.
>
> For the record, I'm extremely leery of the more-is-better approach.
> We seem to be adding a large number of very large APIs, which seems
> to be contrary to the Scheme ideal of small well-chosen primitives
> that work synergistic well together. People were unhappy with R6RS
> because of its size and that so much of it was invention rather than
> codifying existing practice. R7RS-large is the same - but much more so.
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/
>
--
You received this message because you are subscribed to the Google Groups "scheme-reports-wg2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scheme-reports-wg2+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2019-01-18 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 14:27 Tangerine Edition penultimate report: how I voted, how you're voting John Cowan
2019-01-17 0:06 ` John Cowan
2019-01-18 1:14 ` Per Bothner
[not found] ` <00545ca8-81d6-d4c5-5acc-142c87457692-ENPyne5uQy1BDgjK7y7TUQ@public.gmane.org>
2019-01-18 3:34 ` John Cowan
2019-01-18 20:20 ` Ivan Raikov [this message]
[not found] ` <CADM5OqP-jNjhJpbAmS7y8ygjtXY=HGc2Dx-qZyee6o0yB+zquA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-01-19 21:39 ` [scheme-reports-wg2] " John Cowan
[not found] ` <CAD2gp_T88mTd2r6y+e_1WOeLioR8cWEND_ZfTkOJ370VQPEcWA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-01-20 13:11 ` Amirouche Boubekki
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='CADM5OqP-jNjhJpbAmS7y8ygjtXY=HGc2Dx-qZyee6o0yB+zquA@mail.gmail.com' \
--to=ivan.g.raikov@gmail.com \
--cc=chibi-scheme@googlegroups.com \
--cc=chicken-users@nongnu.org \
--cc=cowan@ccil.org \
--cc=gambit-list@iro.umontreal.ca \
--cc=guile-user@gnu.org \
--cc=per@bothner.com \
--cc=scheme-reports-wg1@googlegroups.com \
--cc=scheme-reports-wg2@googlegroups.com \
--cc=srfi-160@srfi.schemers.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).