From: Arne Babenhauserheide <arne_bab@web.de>
To: guile-devel@gnu.org
Cc: "Andy Wingo" <wingo@pobox.com>, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Logo baseline
Date: Sun, 19 Jan 2020 00:47:01 +0100 [thread overview]
Message-ID: <87lfq49vka.fsf@web.de> (raw)
In-Reply-To: <CABsfGyU962uSj0URDTd0VaB6C_uZcCAA91+ZTwSUqMSLNABvqg@mail.gmail.com>
Thomas Morley <thomasmorley65@gmail.com> writes:
>> Clearly, Guile is still an extension language, with many great
>> applications (Gnucash, Lepton-EDA, OpenCog, GDB, etc.)
>
> Well, you forgot LilyPond
The one tool that uses Guile while dominating its domain.
> 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.
Same for me. That Guile takes effort to make extending easy
distinguishes Guile from all the just-scripting languages out there, and
also from many other Schemes.
Actually I’d love to see Guile become better at this: to make it easier
to deploy an application that uses Guile in a statically compiled
binary.
Basically to generalize what LilyPond is doing.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
next prev parent reply other threads:[~2020-01-18 23:47 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
2020-01-18 23:47 ` Arne Babenhauserheide [this message]
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=87lfq49vka.fsf@web.de \
--to=arne_bab@web.de \
--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).