From: Arne Babenhauserheide <arne_bab@web.de>
To: guile-user@gnu.org
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Request for feedback on SRFI-126
Date: Tue, 29 Sep 2015 22:18:04 +0200 [thread overview]
Message-ID: <4816667.WGBHnKbjFh@fluss> (raw)
In-Reply-To: <CAMFYt2b4Cpnjc-BjLCQ4iYTW_5U3N86dwwBJEyrFUKy=UbwV-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Am Sonntag, 27. September 2015, 21:00:46 schrieb Panicz Maciej Godek:
> You wrote there, among others, that "with a little more work, standard
> Scheme might actually become a language essentially as usable as Python and
> the like".
>
> If you're looking for a language that is "as usable as Python", then I'd
> recommend trying out Python, which is very good at what it does.
>
> Maybe I'm reading your point wrong, but I don't think that competing with
> Python or chasing Python or trying to mimic Python would be anything but a
> waste of time
Saying that it should be “as usable as Python” isn’t the same as
saying that it should chase Python or mimic Python. You can make
furniture from wood or steel, but if you only have off-the-shelf
chairs and tables of wood, no one is going to open a restaurant with a
kitchen made of steel. Or built a skyscraper, for that matter.
Making Scheme as usable as Python requires finding an elegance which
fits Scheme and allows creating applications at least as easily as
with Python — but not necessarily in the same style.
Best wishes,
Arne
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 299 bytes --]
next prev parent reply other threads:[~2015-09-29 20:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 12:15 Request for feedback on SRFI-126 Taylan Ulrich Bayırlı/Kammer
2015-09-27 19:00 ` Panicz Maciej Godek
2015-09-27 20:11 ` Taylan Ulrich Bayırlı/Kammer
2015-09-27 23:20 ` Panicz Maciej Godek
2015-09-27 23:56 ` Marko Rauhamaa
2015-09-28 8:13 ` Taylan Ulrich Bayırlı/Kammer
2015-09-28 10:37 ` Marko Rauhamaa
2015-09-28 12:39 ` Taylan Ulrich Bayırlı/Kammer
2015-09-28 20:02 ` Panicz Maciej Godek
2015-09-29 20:05 ` Arne Babenhauserheide
2015-09-29 23:02 ` Panicz Maciej Godek
2015-09-29 23:44 ` Arne Babenhauserheide
2015-09-30 6:39 ` Panicz Maciej Godek
2015-09-30 22:16 ` Arne Babenhauserheide
2015-09-30 23:39 ` Panicz Maciej Godek
2015-09-30 7:58 ` Taylan Ulrich Bayırlı/Kammer
2015-09-30 22:20 ` Arne Babenhauserheide
2015-10-01 7:33 ` Taylan Ulrich Bayırlı/Kammer
2015-09-29 20:18 ` Arne Babenhauserheide [this message]
2015-10-01 5:11 ` Marko Rauhamaa
2015-09-28 15:46 ` Christopher Allan Webber
2015-09-28 17:34 ` Taylan Ulrich Bayırlı/Kammer
2015-09-30 17:41 ` Mark H Weaver
2015-09-30 22:33 ` Taylan Ulrich Bayırlı/Kammer
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=4816667.WGBHnKbjFh@fluss \
--to=arne_bab@web.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).