From: "Ludovic Courtès" <ludo@gnu.org>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: Logo baseline
Date: Mon, 20 Jan 2020 09:35:49 +0100 [thread overview]
Message-ID: <87d0bejziy.fsf@gnu.org> (raw)
In-Reply-To: <87wo9n4ju7.fsf@web.de> (Arne Babenhauserheide's message of "Sun, 19 Jan 2020 15:11:28 +0100")
Hello,
Arne Babenhauserheide <arne_bab@web.de> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>> Like I wrote, Guile remains an extension language, no argument here.
>>
>> However, describing it as “just” an extension language seems odd to me.
>> It doesn’t take into account what many have been doing with Guile, and
>> it doesn’t match the efforts that have gone into Guile since 2.0.
>
> I don’t think that it is described as "just" an extension language. The
> website makes it very clear that Guile is also a viable application
> language.
>
> Where do you get the impression that Guile is described as "just" an
> extension language?
This thread is about the logo baseline, which is: “GNU extension
language”. I agree that the web site is clearer; I’m just talking about
the logo here.
>>> 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.
>>
>> In what ways could it become “better” for this use case?
>
> Currently the default way to embed assumes that Guile is provided as a
> shared library. But that can be problematic when you want to ship a
> binary people can test easily.
I think this is no different for Guile than for any other piece of
software: some would ship a Docker image, and I’d argue that you can use
‘guix pack’ to generate a minimal standalone tarball or Docker image.
(Though I think it’s also perfectly doable to provide a binary that’s
statically-linked against libguile.)
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-01-20 8:35 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
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 [this message]
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=87d0bejziy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=arne_bab@web.de \
--cc=guile-devel@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).