From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: FOSDEM 2019
Date: Tue, 05 Feb 2019 16:26:42 -0500 [thread overview]
Message-ID: <87d0o6c4fh.fsf@dustycloud.org> (raw)
In-Reply-To: <87o97sv51q.fsf@web.de>
Arne Babenhauserheide writes:
> Mikael Djurfeldt <mikael@djurfeldt.com> writes:
>
>> It was a great experience and joy for me to meet some of you at FOSDEM
>> 2019. Thank you all!
>
> Thank you, too!
>
>> Now a piece of advice.
>>
>> Everyone who works with Guile knows that it's crap and look with envy at
>> projects like Chez and Racket, right?
>
> I’ll ignore for a moment that this is a rhethoric method and answer
> directly: No, I don’t think that Guile is crap. It is actually really
> good, and while there are missing parts, I enjoy working in Guile more
> than I enjoy working in Python. Even when I use parentheses :-)
>
> The talk by Christopher Webber basically described the importance of
> shiny — all the bits other people already polished. A similar argument
> cuts for using Python, and even Java.
>
> This does not make it invalid: Chris is right that shiny is important;
> but it is not all-important, especially not in the long run. And
> different from many other projects, Guile takes the long run seriously.
Oops, I misquoted Arne as Janneke in my last email... my bad. :)
next prev parent reply other threads:[~2019-02-05 21:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 21:34 FOSDEM 2019 Mikael Djurfeldt
2019-02-03 23:13 ` Arne Babenhauserheide
2019-02-04 5:21 ` Nala Ginrut
2019-02-05 21:25 ` Christopher Lemmer Webber
2019-02-06 13:46 ` Alex Sassmannshausen
2019-02-06 15:22 ` Amirouche Boubekki
2019-02-06 15:33 ` Amirouche Boubekki
2019-02-06 15:42 ` Alex Sassmannshausen
2019-02-06 21:03 ` Ricardo Wurmus
2019-02-06 22:09 ` Alex Sassmannshausen
2019-02-26 8:57 ` swedebugia
2019-02-06 20:40 ` Arne Babenhauserheide
2019-02-05 21:26 ` Christopher Lemmer Webber [this message]
2019-02-04 13:06 ` Amirouche Boubekki
2019-02-04 14:44 ` Ludovic Courtès
2019-02-04 18:01 ` Jan Nieuwenhuizen
2019-02-05 11:09 ` Amirouche Boubekki
2019-02-05 16:58 ` Ludovic Courtès
2019-02-06 0:31 ` Nala Ginrut
2019-02-06 12:59 ` Ludovic Courtès
2019-02-06 19:09 ` Amirouche Boubekki
2019-02-06 0:37 ` Matt Wette
2019-02-06 0:56 ` Nala Ginrut
2019-02-06 1:40 ` Amirouche Boubekki
2019-02-05 2:30 ` Matt Wette
-- strict thread matches above, loose matches on Subject: below --
2018-08-21 13:33 Manolis Ragkousis
2018-08-21 17:57 ` Ricardo Wurmus
2018-08-22 16:27 ` Andy Wingo
2018-08-22 2:33 ` Mike Gran
2018-08-23 0:08 ` Mike Gran
2018-08-24 12:23 ` Christopher Lemmer Webber
2018-08-29 21:08 ` Ludovic Courtès
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=87d0o6c4fh.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=arne_bab@web.de \
--cc=guile-devel@gnu.org \
/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).