From: David Kastrup <dak@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: Xue Fuqiao <xfq.free@gmail.com>, Alan Mackenzie <acm@muc.de>,
Christopher Allan Webber <cwebber@dustycloud.org>,
bruce.connor.am@gmail.com, emacs-devel <emacs-devel@gnu.org>
Subject: Re: In support of guile-emacs
Date: Mon, 19 Oct 2015 16:50:32 +0200 [thread overview]
Message-ID: <87y4eyj4jr.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <5624FADF.9070908@dancol.org> (Daniel Colascione's message of "Mon, 19 Oct 2015 07:14:55 -0700")
Daniel Colascione <dancol@dancol.org> writes:
> On 10/19/2015 03:24 AM, Alan Mackenzie wrote:
>> Hello, Xue.
>>
>> On Mon, Oct 19, 2015 at 09:07:59AM +0800, Xue Fuqiao wrote:
>>
>>> guile-emacs replaces Emacs's own Emacs Lisp engine with Guile's (without
>>> breaking backward compatibility). So:
>>
>>> * Emacs Lisp will execute faster (Guile VM bytecode is more efficient)
>>
>> Just as a matter of interest, approximately how much faster is Guile
>> bytecode than Emacs bytecode? Are we talking about 10%, 20%, 50%, a
>> factor of 2, or even higher?
>>
>> If that speed increase was significant, it might be worth incorporating
>> Guile's bytecode into Emacs just for that reason, regardless of any of
>> the other stuff.
>
> Or simply making completely independent and custom-tailored
> improvements to the Emacs bytecode compiler and interpreter
> itself. There's no reason to imagine that the only way to improve
> performance there is to move to a completely different runtime.
There is no question that everything that can be done independently of
Emacs can also be done inside of Emacs.
If someone does it. The point of decoupling work on Emacs from work on
the compiling techniques within Emacs is to get more work done from the
total set of people than if everybody reinvents and designs and
maintains his own wheels.
--
David Kastrup
next prev parent reply other threads:[~2015-10-19 14:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 20:48 In support of guile-emacs Christopher Allan Webber
2015-10-18 23:12 ` Artur Malabarba
2015-10-19 1:07 ` Xue Fuqiao
2015-10-19 10:24 ` Alan Mackenzie
2015-10-19 10:27 ` David Kastrup
2015-10-19 14:14 ` Daniel Colascione
2015-10-19 14:35 ` Alan Mackenzie
2015-10-19 16:56 ` Taylan Ulrich Bayırlı/Kammer
2015-10-19 17:19 ` Alan Mackenzie
2015-10-19 18:50 ` Taylan Ulrich Bayırlı/Kammer
2015-10-19 19:03 ` Dmitry Gutov
2015-10-19 19:49 ` Taylan Ulrich Bayırlı/Kammer
2015-10-19 20:12 ` Alan Mackenzie
2015-10-19 21:01 ` Taylan Ulrich Bayırlı/Kammer
2015-10-20 9:53 ` Alan Mackenzie
2015-10-20 20:09 ` Taylan Ulrich Bayırlı/Kammer
2015-10-20 23:46 ` John Wiegley
2015-10-21 12:54 ` Taylan Ulrich Bayırlı/Kammer
2015-10-21 13:13 ` Alan Mackenzie
2015-10-20 6:00 ` David Kastrup
2015-10-19 14:50 ` David Kastrup [this message]
2015-10-19 8:22 ` Tom
2015-10-19 8:38 ` Andreas Schwab
2015-10-19 8:54 ` Tom
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=87y4eyj4jr.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=acm@muc.de \
--cc=bruce.connor.am@gmail.com \
--cc=cwebber@dustycloud.org \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=xfq.free@gmail.com \
/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.