From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Andy Wingo <wingo@pobox.com>, Guile Devel <guile-devel@gnu.org>
Subject: Re: Logo baseline
Date: Sun, 19 Jan 2020 09:14:02 +0100 [thread overview]
Message-ID: <87ftgbq2wl.fsf@gnu.org> (raw)
In-Reply-To: <87a76kx3g2.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 18 Jan 2020 15:08:13 +0100")
Ludovic Courtès writes:
> What’s about you? What’s Guile to you? :-)
Guile is the force that binds GNU together. Guile was intended to
extend (all) GNU programs, truly empowering the user. You made Guile
into a great language for writing programs. Now Guile even creates a
coherent GNU System, through Guix.
Moving from Python to Guile was a gentle path towards a more functional
approach of writing programs which reduces accidental complexity and
fits much better with how my mind works.
What puzzles me is the long road it took me to reach this point, more
than 20 years via C, C++ and Python. When I look at GNU projects like
Glibc or GCC moving from awk/sed/perl to Python for scripts instead of
Guile I can't help thinking: Oh my, they are where I was 20 years ago;
what a long path we still have before us.
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
prev parent reply other threads:[~2020-01-19 8:14 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
2020-01-19 8:14 ` Jan Nieuwenhuizen [this message]
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=87ftgbq2wl.fsf@gnu.org \
--to=janneke@gnu.org \
--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).