unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thomas Morley <thomasmorley65@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Andy Wingo <wingo@pobox.com>, Guile Devel <guile-devel@gnu.org>
Subject: Re: Logo baseline
Date: Sat, 18 Jan 2020 23:57:44 +0100	[thread overview]
Message-ID: <CABsfGyU962uSj0URDTd0VaB6C_uZcCAA91+ZTwSUqMSLNABvqg@mail.gmail.com> (raw)
In-Reply-To: <87a76kx3g2.fsf@gnu.org>

Am Sa., 18. Jan. 2020 um 15:14 Uhr schrieb Ludovic Courtès <ludo@gnu.org>:
>
> Hello Guilers!
>
> The Guile logo has this “GNU extension language” baseline.  As Guile 3
> came out, this baseline felt odd to me, not quite corresponding to the
> way I see Guile.
>
> Clearly, Guile is still an extension language, with many great
> applications (Gnucash, Lepton-EDA, OpenCog, GDB, etc.), and I’m sure
> libguile is here to stay.

Well, you forgot LilyPond

> Yet, to me, “extension language” does not
> accurately capture what Guile today allows for and what people have been
> doing with it; since 2.0, it’s more than an extension language, even
> more so with the performance afforded by Guile 3.
>
> Thus, I’d propose changing the baseline.  Something that would describe
> what Guile is to me is:
>
>   GNU, fast, fun, functional
>
> What’s about you?  What’s Guile to you?  :-)
>
> Ludo’.

Well, for me, Guile's _the_ extension language for my LilyPond.

It may be more, it may have become more.
And yes, I used Guile for some other stuff as well.
Nevertheless, it remains the language to extend LilyPond.

It feels very strange dropping said phrase.


Cheers,
  Harm



  parent reply	other threads:[~2020-01-18 22:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-18 14:08 Logo baseline Ludovic Courtès
2020-01-18 14:33 ` Amirouche Boubekki
2020-01-18 15:08 ` Linus Björnstam
2020-01-18 17:05 ` Matt Wette
2020-01-18 19:40 ` Nala Ginrut
2020-01-18 22:22 ` Arne Babenhauserheide
2020-01-18 22:57 ` Thomas Morley [this message]
2020-01-18 23:47   ` Arne Babenhauserheide
2020-01-19 11:21     ` Ludovic Courtès
2020-01-19 14:11       ` Arne Babenhauserheide
2020-01-19 14:59         ` Matt Wette
2020-01-19 17:40           ` Arne Babenhauserheide
2020-01-20  8:35         ` Ludovic Courtès
2020-01-19  8:14 ` Jan Nieuwenhuizen

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=CABsfGyU962uSj0URDTd0VaB6C_uZcCAA91+ZTwSUqMSLNABvqg@mail.gmail.com \
    --to=thomasmorley65@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=wingo@pobox.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).