From: Arne Babenhauserheide <arne_bab@web.de>
To: guile-devel@gnu.org
Cc: Andy Wingo <wingo@pobox.com>
Subject: Re: Logo baseline
Date: Sat, 18 Jan 2020 23:22:34 +0100 [thread overview]
Message-ID: <87muak9zh1.fsf@web.de> (raw)
In-Reply-To: <87a76kx3g2.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> 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.
What do you mean about the logo? Do you mean tagline? Where I see a
tagline is at the website: https://www.gnu.org/software/guile/
As one point of several we have there:
"Guile is an extension language platform
…
Guile is the GNU Ubiquitous Intelligent Language for Extensions, and
the official extension language of the GNU project."
That’s an important statement, one which brought me to Guile, because
this gives Guile purpose beyond only being a useful language. It is the
language to extend GNU programs.
But aside from this, the website also says:
- Guile is a programming language -> create applications (this is what it starts with!)
- Extend applications (which actually talks about implementing languages in Guile)
- Guile empowers users with "practical software freedom"
The Reference manual says
"GNU's Programming and Extension Language"
https://www.gnu.org/software/guile/static/base/img/covers/guile-reference.png
So the material already states clearly that Guile is not only for extension.
However that extending applications is part of the story is an important
point for me: This also implies that it’s easy to move parts of my
application into the fastest language I can find.
It’s unlikely that Guile will beat C for raw performance *and* memory
requirements for the most performance-critical part of an application,
so knowing that I can shift that part into C (or C++ or Rust or anything
else with C-bindings) is an important point.
Being able to easily embed Guile in a C++ application is a
distinguishing feature compared to Python. That way Guile strikes a
middle-point between Python and Lua.
Also I would love to have a way to script a Godot-game with Guile:
https://godotengine.org/
> 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? :-)
It is the language where I can best experiment with pushing the
boundaries of programming without having to write my own compiler.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
next prev parent reply other threads:[~2020-01-18 22:22 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 [this message]
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
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=87muak9zh1.fsf@web.de \
--to=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).