unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: A0 <cape.wrath@openmailbox.org>
To: guile-user@gnu.org
Subject: Re: Request for feedback on SRFI-126
Date: Mon, 28 Sep 2015 10:24:08 +0100	[thread overview]
Message-ID: <56090738.1060604@openmailbox.org> (raw)
In-Reply-To: <CAMFYt2bKtaUPy2di=c6G9ezc-2KDR0inoOVfcYAVxU5np2gQxw@mail.gmail.com>



On 28/09/15 00:20, Panicz Maciej Godek wrote:
> Delimited continuations are an academic curiosity, and sockets and
> regexps are just a specific domain (I'm sure you could easily find
> plenty of others; anyway, they are by no means fundamental)


Sorry, but I have to comment on this. So did people think of lambdas,
map, reduce and the rest
of list/array collective manipulation procedures, but look at the new
Java/C++ et al standards. It just
so happened that they have implemented them decades after they
achieved their normal use
in languages like Lisp and Scheme. I wonder when we'll finally get
tail calls and named lets  in the
mainstream languages :).

I fully understand Taylan's point of view. Scheme has more expressive
power than any other dynamic
language I have encountered. I am trying to use it for day-to-day
tasks which used to be difficult
only because the batteries were not included. Maybe for you it's a
nice little language to demo great
coding ideas, but it can be a practical platform as Guile
demonstrates. Unfortunately for the novice programmers
the practicality of Guile only becomes clear after one can use its
nifty FFI to patch up the
still unimplemented features.

In a sense, I don't think it is so necessary to have a practical
Scheme standard as long as there is at
least one implementation that can be used to perform with ease 90% of
tasks a modern programmer needs to
tackle. And, yeah, I'd love to see the core scheme kept clean.

All the best...



  parent reply	other threads:[~2015-09-28  9:24 UTC|newest]

Thread overview: 25+ 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-28  9:24       ` A0 [this message]
2015-09-29 20:18   ` Arne Babenhauserheide
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=56090738.1060604@openmailbox.org \
    --to=cape.wrath@openmailbox.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).