unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Bill Schottstaedt" <bil@ccrma.Stanford.EDU>
To: ludovic.courtes@laas.fr (Ludovic Courtès),
	"Marco Maggi" <marco.maggi-ipsu@poste.it>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: the future of Guile
Date: Tue, 4 Dec 2007 06:50:19 -0800	[thread overview]
Message-ID: <20071204144743.M4841@ccrma.Stanford.EDU> (raw)
In-Reply-To: <87wsrupr8a.fsf@laas.fr>

> Right, although I question the "language for extensions" paradigm: why 
> would you choose language Y for "extensions" and language X for the 
> rest, given that (i) X sucks, (ii) Y rocks, and (iii) nothing inherently 
> makes programs in language Y "slower".  :-) 

There are several reasons to have different base and extension
languages.  The worst is that Guile/Scheme is 10 to 30 times
slower than the equivalent C code, and in DSP work, that matters.
For stuff involving vectors, C is much easier to read than Scheme.
Another is that everyone has his favorite language, and
by separating the basic stuff out, you can provide any number
of extension language choices at reasonably small cost (Snd
can be built with Guile, Gauche, Forth, Ruby, or no extension
language).  I've seen this "There is one Language and its
name is XXX" about 40 times -- at least once for every language
except maybe Pascal.  Of course, it was true in SAIL's case...




_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2007-12-04 14:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04  6:50 the future of Guile Marco Maggi
2007-12-04  8:48 ` Stephen Compall
2007-12-04 12:41 ` Ludovic Courtès
2007-12-04 14:50   ` Bill Schottstaedt [this message]
2007-12-04 15:30     ` Ludovic Courtès
2007-12-04 23:00 ` Neil Jerram
2007-12-05 23:11 ` Andy Wingo
2007-12-06 19:48 ` Mikael Djurfeldt
     [not found] <F8.1B.18780.B4965574@avas11>
2007-12-04 15:55 ` the future of guile Daniel Llorens del Río
     [not found] <cmu-lmtpd-7104-1196779864-1@mail-imap2.uio.no>
2007-12-04 18:08 ` the future of Guile Kjetil S. Matheussen
2007-12-04 18:34   ` Kjetil S. Matheussen
2007-12-04 20:06     ` Roland Orre
2007-12-04 20:42       ` Ludovic Courtès
2007-12-04 22:30       ` Kjetil S. Matheussen
     [not found] <34.F3.20110.D6985574@avas19>
2007-12-04 19:54 ` the future of guile Daniel Llorens del Río
  -- strict thread matches above, loose matches on Subject: below --
2007-12-05  9:01 the future of Guile Marco Maggi
2007-12-05 14:19 ` Roland Orre
2007-12-05 20:28 ` Ludovic Courtès
2007-12-05 15:40 Mike Gran
2007-12-05 16:05 ` Julian Graham
2007-12-05 16:18 ` Daniel Ridge
2007-12-05 20:41 ` Ludovic Courtès
2007-12-05 21:02 Marco Maggi
2007-12-05 22:32 Marco Maggi
2007-12-05 22:56 ` Ludovic Courtès
     [not found] <cmu-lmtpd-27643-1196871540-1@mail-imap2.uio.no>
2007-12-06 14:52 ` Kjetil S. Matheussen
2007-12-07  6:28 Marco Maggi
     [not found] <cmu-lmtpd-4316-1197047238-3@mail-imap2.uio.no>
2007-12-07 17:42 ` Kjetil S. Matheussen

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=20071204144743.M4841@ccrma.Stanford.EDU \
    --to=bil@ccrma.stanford.edu \
    --cc=guile-user@gnu.org \
    --cc=ludovic.courtes@laas.fr \
    --cc=marco.maggi-ipsu@poste.it \
    /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).