all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: Guile vs ELisp
Date: Thu, 04 Nov 2010 18:10:57 +1100	[thread overview]
Message-ID: <87sjzhtvge.fsf@puma.rapttech.com.au> (raw)
In-Reply-To: mailman.4.1288834774.2711.help-gnu-emacs@gnu.org

Dani Moncayo <dmoncayo@gmail.com> writes:

> Hi there,
>
> I'm a beginner in Elisp, and have a question (just for curiosity):
>
> Go to the Emacs Lips Manual (edition 3.0 / Emacs 24.0.50), section
> "1.2 Lisp History". The last paragraph reads like this:
>
>>    Emacs Lisp is not at all influenced by Scheme; but the GNU project
>> has an implementation of Scheme, called Guile.  We use Guile in all new
>> GNU software that calls for extensibility.
>
> ...so my question is: If GNU Emacs was to be started from scratch
> today, would Guile be better than ELips as extensibility language?
>

In short, yes, guile would probably be a better extension language than
elisp, which has some real limitations. There has been a lot of
discussion about this over the years. In general, most acccept that
guile would be better, but the issue is all the legacy elisp code that
would be lost and the amount of work that would need to be done to get
the same level of functionality we already have. 

While we may see an emacs like editor with guile as the extension
language at some point in the future, though I doubt it, I suspect it
will be a totally new beastie. Imagine an emacs that is multi-threaded,
has an extension language with namespaces, closures, etc and can start
without any of the old 'baggage' and learns from the wealth of
experience gained over the past 40 years. Could be a truely wonderful
thing. At the same time, consider all the effort and work that has gone
into the fine editor we now have and the amount of work it would take to
get the same functionality - a huge task. Then combine that with the
wealth of alternatives and the fact I think most people are now use to
using many different programs. There is an argument that would suggest
we are better off with distinct programs that all do one thing, but do
it really well rather than one large program that tries to do
everything. If you use emacs just as an editor, what level of power do
you really need in an extension language. While elisp may have some real
limitaitons, most of these don't greatly impact on things you want to do
with it that are diretly relevant to an editor. Most of the limitations
apear to become an issue when you start writing extensions to do things
other than those directly relating to editing of text i.e. web browser,
mail readers, chat /IM clients, etc. 

Tim



-- 
tcross (at) rapttech dot com dot au


  parent reply	other threads:[~2010-11-04  7:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.4.1288834774.2711.help-gnu-emacs@gnu.org>
2010-11-04  1:52 ` Guile vs ELisp Jason Earl
2010-11-04 10:38   ` Richard Riley
2010-11-04  7:10 ` Tim X [this message]
     [not found] ` <de03fb13-8efb-495c-9112-36bf1abd1cc4@v20g2000yqb.googlegroups.com>
2010-11-05  2:16   ` Elena
2010-11-03 23:11 Dani Moncayo
2010-11-04 15:38 ` Thien-Thi Nguyen
2010-11-04 16:17   ` Tassilo Horn
2010-11-09 14:45   ` Dani Moncayo
2010-11-04 16:32 ` Stefan Husmann
2010-11-04 19:59   ` Jose A. Ortega Ruiz

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sjzhtvge.fsf@puma.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --cc=help-gnu-emacs@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.