unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: John Cowan <cowan@ccil.org>
To: Massimiliano Gubinelli <m.gubinelli@gmail.com>
Cc: guile-user <guile-user@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: rfc: next guile 1.8.x release
Date: Sun, 7 Feb 2021 01:59:58 -0500	[thread overview]
Message-ID: <CAD2gp_QD48AZA+1Obw9XM0Ad_Rsi0zWE1P2pYTcwZtcAw4uw1g@mail.gmail.com> (raw)
In-Reply-To: <B138465C-766D-43E8-AABC-0E5081FD004D@gmail.com>

On Sun, Jan 31, 2021 at 12:36 PM Massimiliano Gubinelli <
m.gubinelli@gmail.com> wrote:


> Chibi is too slow


I'll just mention here that Chibi's file include/chibi/features.h has many
feature macros (at the C level) that can be changed to make Chibi
smaller/faster: for example, you could disable Unicode support, R7RS module
support, etc.  If you do that, rebuild, and re-benchmark, the results might
be more pleasant.  There would still be the issue of making whatever
changes are required to adapt the existing code to Chibi, of course.

> So Guile 1.8 today remains a very good piece of software,


I propose (and I think this would make the Guile team happier) that you
fork Guile 1.8.x into a new project with a new name (Canny Scheme, Foxy
Scheme, or Sneaky Scheme, perhaps?).  That way you can maintain it for
your own use, it will be easier for packagers to work with since it will
have its own version number sequence, and it will be available to others
who want small, fast, somewhat Guile-compatible code.

Whether this would be a GNU project or not would need to be resolved by the
powers that GNU, of course.

In my mind Guile 1.8 is a very different language than Guile 2/3


Agreed: a different dialect of Scheme should have its own name.



John Cowan          http://vrici.lojban.org/~cowan        cowan@ccil.org
C'est la` pourtant que se livre le sens du dire, de ce que, s'y conjuguant
le nyania qui bruit des sexes en compagnie, il supplee a ce qu'entre eux,
de rapport nyait pas.               --Jacques Lacan, "L'Etourdit"


  parent reply	other threads:[~2021-02-07  6:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 21:54 rfc: next guile 1.8.x release Thien-Thi Nguyen
2021-01-11 14:51 ` Mike Gran
2021-01-12 10:55   ` Massimiliano Gubinelli
2021-01-16 22:55     ` Thien-Thi Nguyen
2021-01-16 22:48   ` Thien-Thi Nguyen
2021-01-29 21:35 ` Ludovic Courtès
2021-01-29 23:46   ` Dr. Arne Babenhauserheide
2021-01-30 12:31     ` Ricardo Wurmus
2021-01-30 14:49       ` Dr. Arne Babenhauserheide
2021-01-31 17:35       ` Massimiliano Gubinelli
2021-02-01 21:49         ` Ludovic Courtès
2021-02-07  6:59         ` John Cowan [this message]
2021-03-08 20:36 ` Andy Wingo
2021-03-09  7:14   ` Dr. Arne Babenhauserheide
2022-03-03  0:11     ` Thien-Thi Nguyen
2022-03-14 12:14       ` Thien-Thi Nguyen

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=CAD2gp_QD48AZA+1Obw9XM0Ad_Rsi0zWE1P2pYTcwZtcAw4uw1g@mail.gmail.com \
    --to=cowan@ccil.org \
    --cc=guile-user@gnu.org \
    --cc=ludo@gnu.org \
    --cc=m.gubinelli@gmail.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).