From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: Mike Gran <spk121@yahoo.com>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: guile 2012
Date: Tue, 17 Jan 2012 16:27:58 -0800 [thread overview]
Message-ID: <CA+XASoX1Hyo+Py+8BeEbMQXZAg_Cp1hkU7GebaiHFQb1yEdZLw@mail.gmail.com> (raw)
In-Reply-To: <1326839820.34640.YahooMailNeo@web37901.mail.mud.yahoo.com>
I feel like I shouldn't get into this discussion for my huge lack of
Guile (and Scheme in general) knowledge. But I will do in any case
:-).
On Tue, Jan 17, 2012 at 2:37 PM, Mike Gran <spk121@yahoo.com> wrote:
> <heresy>
[snip]
> I know that you want to believe that if your tech is good enough,
> people will learn Scheme. For many people, that just won't ever happen.
> It will always be a blocker for increasing the popularity of Guile.
>
> (Did I just propose Dylan?)
> </heresy>
>
I disagree a bit with this point. People will learn Gule if there are
nice libraries around it (what you said before). People is learning
Clojure and it's being using for real work, and it has parenthesis.
Ruby doesn't have parenthesis, but without Rails, may be it would have
just been another language. Now there's hundreds of companies,
freelancers that base their work in Ruby on Rails. And I'm sure
there's plenty of more cases.
I agree with the weakness of installing 3rd party libraries. I'm
afraid that's true for every language.
Guildhall will probably save Guile from being just another language
used by a few.
That was my half cent. :-)
Aleix
next prev parent reply other threads:[~2012-01-18 0:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 2:34 guile 2012 Andy Wingo
2012-01-12 22:50 ` Ludovic Courtès
2012-01-13 22:21 ` Dirk-Jan C. Binnema
2012-01-17 22:37 ` Mike Gran
2012-01-18 0:27 ` Aleix Conchillo Flaqué [this message]
2012-01-19 12:27 ` Nala Ginrut
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=CA+XASoX1Hyo+Py+8BeEbMQXZAg_Cp1hkU7GebaiHFQb1yEdZLw@mail.gmail.com \
--to=aconchillo@gmail.com \
--cc=guile-devel@gnu.org \
--cc=spk121@yahoo.com \
--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).