From: Lassi Kortela <lassi@lassi.io>
To: Per Bothner <per@bothner.com>,
Arvydas Silanskas <nma.arvydas.silanskas@gmail.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: Time for a new release? 3.1.2?
Date: Fri, 6 Jan 2023 14:16:06 +0200 [thread overview]
Message-ID: <20b2efef-24af-ff6f-6591-db5c695a7d74@lassi.io> (raw)
In-Reply-To: <a0d4768d-db63-f9b5-d3f4-bfb54c870c6e@bothner.com>
> I think the R7RS-large process is off-track, and is unlikely to reach
> any useful destination
> without a fundamental course-correction. Piling on more and more
> different-but-similar
> libraries is not the way to do a programming language in the 21st
> century. Even Common Lisp
> realized that different differently-named functions for every useful
> data-type is not
> good language design.
>
> Scheme needs some way to define "interfaces"/"traits" that multiple
> data-types
> can implement. Many Scheme implementations (including Kawa) have that,
> but a
> general portable solution is highly desired. Without that, there is no
> point
> in piling on more and more libraries for more and more data types.
>
> I am not the only one who feels this way, as you can see from the
> SRFI/R7RS mailing lists.
Thank you for saying this, Per. Agreed on all counts.
We just had another round of discussions on the SRFI lists. Like the
earlier ones, it went nowhere. The core group cannot examine its own
flaws. I'm leaving and starting alternatives.
next prev parent reply other threads:[~2023-01-06 12:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 17:53 Duncan Mak
2022-09-29 4:38 ` Per Bothner
2022-09-29 15:18 ` Arvydas Silanskas
2022-10-03 11:36 ` Arvydas Silanskas
2022-10-21 9:01 ` Arvydas Silanskas
2022-10-27 4:50 ` Shawn Wagner
2022-12-06 9:07 ` Arvydas Silanskas
2023-01-05 21:34 ` Per Bothner
2023-01-05 22:02 ` Damien Mattei
2023-01-06 12:16 ` Lassi Kortela [this message]
2023-01-08 18:11 ` Sascha Ziemann
2023-01-09 9:03 ` Lassi Kortela
2023-01-09 9:42 ` Arvydas Silanskas
2023-01-09 10:51 ` Lassi Kortela
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=20b2efef-24af-ff6f-6591-db5c695a7d74@lassi.io \
--to=lassi@lassi.io \
--cc=kawa@sourceware.org \
--cc=nma.arvydas.silanskas@gmail.com \
--cc=per@bothner.com \
/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).