From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailtransmit04.runbox.com (mailtransmit04.runbox.com [IPv6:2a0c:5a00:149::25]) by sourceware.org (Postfix) with ESMTPS id F267E3858C30 for ; Thu, 5 Jan 2023 21:34:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org F267E3858C30 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=bothner.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=bothner.com Received: from mailtransmit02.runbox ([10.9.9.162] helo=aibo.runbox.com) by mailtransmit04.runbox.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1pDXsZ-001LG1-7k; Thu, 05 Jan 2023 22:34:27 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bothner.com ; s=selector2; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID; bh=G3cJotrlmYwdU0Dkqmy6GKL53v2pQFct3IrHbXZ8sBc=; b=KYLeLYtCzyzOkj8IqRUUywYaoW SsT1Ltg4f+ZkhjqedRhAp00DMmdSp8ix1OkERZA1lqE1FM4eLQsoFKlWONzZgdqZFg2N1d/i54P6L hRpTBZDoyzIJ0HYeDrn3qlSj2ZCy6sAwsNcmrhmIlSKZxsLNJk+9ssQye/uxTktB6x4RTlm83O38k m/cXTZUEnf9xdy+3E7gEB+u4D89g1UIPG+5NL+ZzlTyY6uNpfP4ka+gOo94E6zotq9cXglbIzcQRZ 2hwuRqDoItwI8DxWhYnU4+fw/A+M9q0a+TMqEgWQCuI4op6oeJKUwBV22zDq67d2fM1pocODMcslL wxsaiOyg==; Received: from [10.9.9.73] (helo=submission02.runbox) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1pDXsY-0002lh-Q9; Thu, 05 Jan 2023 22:34:26 +0100 Received: by submission02.runbox with esmtpsa [Authenticated ID (524175)] (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) id 1pDXsJ-0003Gi-JB; Thu, 05 Jan 2023 22:34:11 +0100 Message-ID: Date: Thu, 5 Jan 2023 13:34:03 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Subject: Re: Time for a new release? 3.1.2? To: Arvydas Silanskas Cc: kawa mailing list References: <0aee6f41-9f36-e9ef-6761-e8d81a3b5f5f@bothner.com> Content-Language: en-US From: Per Bothner In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 12/6/22 01:07, Arvydas Silanskas wrote: > I'd like to bump a question, would we want to add (for the time being considering only red and tangerine) R7RS-large support? I'm fine with doing necessary work as far as human resources go, but I want to know that this is a direction that people agree with. 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. -- --Per Bothner per@bothner.com http://per.bothner.com/