unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: bitwize@wizards-of-source.org
Subject: Re: Roadmap and goals?
Date: Thu, 18 Apr 2002 16:58:25 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0204181636520.19122-100000@phantom.h07.org> (raw)
In-Reply-To: <m3u1qanisk.fsf@laruns.ossau.uklinux.net>

On 17 Apr 2002, Neil Jerram wrote:

> 
> Some of the things that interest me are: documentation, both manual
> and online; debugging facilities; Emacs integration; libguile
> factorization; Elisp translation.

It may be too much to ask, but I'd like to see a VM being integrated into 
guile-core. The one that Keisuke Nishida wrote a while back is supposedly 
really good; integrating it so that byte-compilation and execution of 
bytecodes becomes the default method of interpretation and execution (much 
as it is with mzscheme) would be a Good Thing for Guile, performance-wise.

Another thing is, I use Guile where many hackers would choose Perl or 
Python, as an all-purpose automation and glue language. It's there, it 
works, and Scheme is much easier to write things quickly in than those 
other languages. Anything that boosts Guile from a systems integration 
standpoint would be nice for my uses. Responding to .NET, SOAP, and all 
that hype-based hoopla with efficient Scheme-based simple RPC and 
secure mobile code mechanisms would be nifty.

That's my wish list for the time being. The TODO also mentions a decent 
Guile binding for Tk. I'm currently working on this using pTk; has anyone 
gotten any further?

> For me I think the answers are (i) because it's GNU (ii) because it's
> what I'm now familiar with, which makes me inclined to stick at it
> until we get it right.  Plus in all the things that I've tried to do
> with it, I've not yet hit any insurmountable technical or
> philosophical barrier - it mostly "just works."

The fact that "it's GNU" is perhaps instrumental to Guile's success. 
Scheme has overall been slapped with the Pascal stigma: it's an 
"educational language", which means it lacks utility in the Real World. 
Guile represents disproof by counterexample, by being quite central to 
many of the things GNU is doing (GNOME, etc.).

> Allegedly Guile is good for integration with C projects, but to be
> honest I haven't evaluated the competition.

SIOD may actually be better in this regard, because of its tiny size and 
liberal license. But then again, SIOD lacks RnRS compliance, and much of 
the other niftiness that Guile has.

-- 
Jeffrey T. Read
"LOBSTER STICKS TO MAGNET!"


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2002-04-18 14:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 12:21 Roadmap and goals? Tanel Tammet
2002-04-17 20:59 ` Neil Jerram
2002-04-18  8:37   ` Panagiotis Vossos
2002-04-19  9:14     ` Panagiotis Vossos
2002-04-20  6:58       ` Thien-Thi Nguyen
2002-04-20 10:18         ` Panagiotis Vossos
2002-04-18 14:58   ` bitwize [this message]
2002-04-18 19:26     ` Rob Browning
2002-04-20  7:23   ` Thien-Thi Nguyen
2002-04-18  0:57 ` Christopher Cramer
2002-04-19 17:36   ` Marius Vollmer
2002-04-19  8:38 ` Nicolas Neuss
2002-04-21 15:14   ` Rob Browning
2002-04-21 22:26   ` bitwize
2002-04-22 18:36     ` Kirill Lisovsky
2002-04-23  7:53       ` rm
2002-04-23 15:11         ` Rob Browning
2002-04-20  7:47 ` Thien-Thi Nguyen
2002-05-14  8:26   ` Thien-Thi Nguyen
  -- strict thread matches above, loose matches on Subject: below --
2002-04-20 12:55 Kirill Lisovsky
2002-04-20 20:01 ` Rob Browning

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=Pine.LNX.4.44.0204181636520.19122-100000@phantom.h07.org \
    --to=bitwize@wizards-of-source.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).