unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: Tanel Tammet <tammet@staff.ttu.ee>, guile-devel@gnu.org
Subject: Re: Roadmap and goals?
Date: Sun, 21 Apr 2002 10:14:58 -0500	[thread overview]
Message-ID: <87sn5pqe19.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87sn5sxevl.fsf@ortler.iwr.uni-heidelberg.de> (Nicolas Neuss's message of "19 Apr 2002 10:38:06 +0200")

(including guile-user since a copy was posted there too)

Nicolas Neuss <Nicolas.Neuss@iwr.uni-heidelberg.de> writes:

> Unfortunately, all those goals are very questionable.  First, non-lisp
> languages get more and more of Lisp's capabilities[1] and the
> advantage is not large any more, especially for the spartanic Scheme
> branch.

Even if that were true, to me that's a little like saying that there's
no reason Perl programmers shouldn't switch to Python, or Tcl to Perl,
or ... since they can do roughly the same things (presuming the
languages in question can do mostly the same things).

>  Second, my guess is that most applications are written within one
> language, because maintaining the interface between two languages is
> a problem.

Could be, and it deppends on what you mean bu "written within" but to
me the Gimp, Guppi, Gnucash, Emacs, snd, and Gnumeric are notable
counter-examples.

> Third, replacing Elisp with Common Lisp would probably be both
> easier and better (but is still difficult, see below).

I haven't checked, but I'd be a little concerned about size.  Last CL
implementation I looked at in much detail was quite large, but perhaps
that's not true anymore.

> Fourth, more liberal licenses than the GPL (e.g. some BSD license)
> or GPLed software not maintained by the FSF is also a nice thing[2].

Not sure if you know, but Guile's license has changed, it's no longer
covered under the GPL alone, there's an exception clause that allows
it to be linked against other applications without causing them to
automatically be covered under the GPL.  See the Guile copyright for
the precise terms.

> Fifth, emulating languages in an integrating way is easy to say, but
> difficult to work out (this is proved by Guile not emulating one
> single other language in a reasonable way).

I consider this an open question -- guile may or may not ever end up
emulating a large number of languages other than elisp, but after the
recent work, I do have reasonable hope for elisp.  <shrug>, we'll see.

> [2] It seems that while the GNU system being under the GPL is
>     certainly achievable, it does not really work that the FSF is the
>     copyright hodler of all essential parts.  This goal should be
>     abandoned.

I can't speak for RMS, but based on my experience, this is a
non-starter, and now that I understand the issues and have seen the US
legal system in action, I can understand the reasoning.

> [4] IMHO, it is a terrible nonsense that people work on so many Scheme
>     implementations in parallel, only to feed the egos of their
>     respective leaders.

You and me both -- what other possible reason could people have for
working on anything but Guile? ;>

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

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


  reply	other threads:[~2002-04-21 15:14 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
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 [this message]
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=87sn5pqe19.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    --cc=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).