unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: guile-user@gnu.org
Subject: Re: Why is guile still so slow?
Date: Thu, 13 Oct 2011 01:56:32 +0200	[thread overview]
Message-ID: <87fwixlq6n.fsf@gnu.org> (raw)
In-Reply-To: 20111012224036.GA2463@happyleptic.org

On Thu, Oct 13 2011, rixed@happyleptic.org wrote:

[...]

>> I really hope that that's not Guile's primary goal these days (and my
>> understanding is that it is not): i wouldn't be much interested if those
>> were its goals ("orchestrator of business oriented code" sounds
>> particularly dreadful :-)).
>
> By "business oriented code" I meant "business logic", ie. the actual
> low level and specialized part of the program. For instance I do system
> programming and cannot do it in scheme (whatever the implementation),
> although scheme is perfect to control the higher levels of abstraction or
> interaction with the user.

Couldn't you use the FFI? I haven't used Guile's yet, but hooking to
inotify in Racket was a breeze...  Of course, if C-level performance is
a requirement, you'd need to switch to a CL compiler ;-)

> "business oriented code" sounds indeed dreadful. I need some vacation
> (in an English speaking country for instance). :)

Barcelona is sunny most of the year, and Wingo speaks quite idiomatic
American and Scheme :)

Cheers,
jao
-- 
To kill time is not murder, it's suicide. -William James (1842-1910)




  reply	other threads:[~2011-10-12 23:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 14:54 Why is guile still so slow? John Lewis
2011-10-12 15:39 ` rixed
2011-10-12 18:56   ` Jose A. Ortega Ruiz
2011-10-12 22:40     ` rixed
2011-10-12 23:56       ` Jose A. Ortega Ruiz [this message]
2011-10-13  6:23         ` rixed
2011-10-13 10:22     ` Andy Wingo
2011-10-13 11:27       ` A bit further toward the flamewar rixed
2011-10-13 14:26         ` Ludovic Courtès
2011-10-13 15:20           ` Andy Wingo
2011-10-13 16:30             ` Linas Vepstas
2011-10-13 18:37               ` Mike Gran
2011-10-13 21:42                 ` Linas Vepstas
2011-10-13 22:08                   ` dskr
2011-10-14  1:07                   ` Ian Price
2011-10-14  8:40                     ` Andy Wingo
2011-10-14 16:23                     ` Linas Vepstas
2011-10-15  8:44                       ` Andy Wingo
2011-10-14  8:28                   ` Andy Wingo
2011-10-14 16:30                     ` Linas Vepstas
2011-10-14 17:26                       ` Andy Wingo
2011-10-13 19:16               ` Hans Aberg
2011-10-14  9:57               ` Panicz Maciej Godek
2011-10-13 17:43             ` Ludovic Courtès
2011-10-13 18:54           ` rixed
2011-10-13 21:14             ` Ludovic Courtès
2011-10-13 21:58               ` Hans Aberg
2011-10-14  9:28                 ` Ludovic Courtès
2011-10-14 10:53                   ` Hans Aberg
2011-10-14  9:37               ` rixed
2011-10-14 20:05                 ` Ludovic Courtès
2011-10-12 15:52 ` Why is guile still so slow? Andy Wingo
2011-10-12 16:19 ` John Lewis

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=87fwixlq6n.fsf@gnu.org \
    --to=jao@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).