From: Tanel Tammet <tammet@staff.ttu.ee>
Subject: Roadmap and goals?
Date: Wed, 17 Apr 2002 15:21:47 +0300 [thread overview]
Message-ID: <3CBD68DB.2CC96A4F@staff.ttu.ee> (raw)
Hi,
This here looks like a troll, but it isn't.
I am sure the same question is asked now and then.
I looked through the site and part of email archives,
but could not find answers to my questions there.
Hence I am trying my luck with the mailing list :-)
Basically, I am wondering if anybody could tell
me something about the Guile development goals
and roadmap: what are the short-term goals,
what are the long-term goals, what are the priorities
(I mean concrete issues, not just the abstract
goal of being a good extension language).
I am asking since I was considering whether I
could possibly help with the development work.
To do that, I'd have to understand where is
the Guile development moving, what are the prioritized
goals, crucial principles, etc. What would be
the projects inside Guile where a person
like me could possibly help.
Some background:
I am the original author of the Hobbit Scheme->C
compiler for SCM and although I did not work on
improving it for some years, I have recently
taken it up again and worked a little on Hobbit
and SCM with Aubrey. I plan to continue making small
improvements for Hobbit for SCM. I can understand
the scope and goals of SCM and what are
the issues with which I could possibly help.
I am pretty happy with SCM. I have looked
briefly into bigloo and other systems, and
there are many cool things here and there.
However, I cannot really understand
(*) what is the driving force behind Guile and
(*) what are the specific benefits of using Guile.
For example, why exactly should somebody
use Guile instead of SCM or Bigloo:
what are the specific advantages and
what is the downside. Why not use just
SCM or Bigloo (they are faster, you know :-)
There have to be answers to this question,
just that I do not know the answers.
In my brief encounters with other people
using scheme these issues have come up
now and then.
I guess it would benefit not only me
but the Guile development and acceptance
on a wider scale if such guides, policies,
roadmaps etc existed and were easy to locate.
Regards,
Tanel Tammet
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-04-17 12:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 12:21 Tanel Tammet [this message]
2002-04-17 20:59 ` Roadmap and goals? 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
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=3CBD68DB.2CC96A4F@staff.ttu.ee \
--to=tammet@staff.ttu.ee \
/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).