From: Richard Todd <richardt@vzavenue.net>
Cc: Pierre Bernatchez <pbz@ogopogo.biz>,
Guile user mailing list <guile-user@gnu.org>
Subject: Re: Guile is a great idea, but where's the community?
Date: Sun, 21 Dec 2003 18:04:29 -0600 [thread overview]
Message-ID: <3FE6350D.4030208@vzavenue.net> (raw)
In-Reply-To: <87ekuxyggx.fsf@marc0.dyndns.org>
Marco Parrone (marc0) wrote:
> IMHO what is missing is code to use, libraries, IMHO it's not worthy
> the fact that it is standardized or not.
Well, the reason to get them organized and collected is so that you can
write new guile code and just assume that users will have the modules
you depend on. If you depend on lots of independent libraries, with
varying standards for documentation, packaging, backwards-compatibility,
and installation, then many would-be users will pass you by. Not to
mention the fact that, based on the guile projects web page, sites with
interesting-sounding guile code have a habit of disappearing.
> For example I'm developing a mail-to-news
> (http://www.nongnu.org/mail-to-news) gateway in Guile Scheme, and I'm
> finding myself implemeting almost only things already implemented in
> Emacs, and now I'm considering rewriting the program in Elisp - thing
> that I think will take much less time than finishing it in Guile
> Scheme. As both Guile Scheme and Emacs Lisp are good languages, I can
> not justify myself the work required to duplicate the efforts.
In terms of guile, I would think the best thing to do is finish it in
scheme, and release all the Emacs-like functionality separately in the
form of re-usable modules. That way, you will be the last person who
has to go through this pain. IMHO, efforts like that will gain the
project the momentum it needs to grow a community of users like the OP
was asking for. The library project I'm proposing would give those
modules a place to live, get them into the hands of guile users, and
guarantee certain standards of quality and consistency.
Richard Todd
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-12-22 0:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-21 17:04 Guile is a great idea, but where's the community? Pierre Bernatchez
2003-12-21 19:58 ` Richard Todd
2003-12-21 22:05 ` Marco Parrone (marc0)
2003-12-22 0:04 ` Richard Todd [this message]
2003-12-22 11:03 ` Neil Jerram
2003-12-22 19:10 ` a.rottmann
2003-12-22 19:36 ` Neil Jerram
2003-12-24 16:45 ` ice-9 Brian S McQueen
2003-12-24 18:06 ` ice-9 Thien-Thi Nguyen
2003-12-24 18:22 ` ice-9 Tom Lord
2004-01-01 22:23 ` Emacs and Guile status (was Re: Guile is a great idea, but where's the community?) Ken Raeburn
2004-01-02 22:36 ` Tim Johnson
2004-01-04 12:25 ` Neil Jerram
2003-12-21 23:10 ` Guile is a great idea, but where's the community? Neil Jerram
2003-12-22 17:02 ` Richard Todd
2003-12-22 5:23 ` Robert Uhl
2003-12-21 22:40 ` Neil Jerram
2003-12-22 3:15 ` Pierre Bernatchez
2003-12-22 7:21 ` Thien-Thi Nguyen
2003-12-22 17:38 ` Thamer Al-Harbash
2003-12-22 19:04 ` Guile/Scheme development Brian S McQueen
2003-12-22 20:08 ` Bruce Korb
2004-01-21 14:02 ` Thien-Thi Nguyen
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=3FE6350D.4030208@vzavenue.net \
--to=richardt@vzavenue.net \
--cc=guile-user@gnu.org \
--cc=pbz@ogopogo.biz \
/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).