From: Ken Raeburn <raeburn@raeburn.org>
To: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Why Emacs should have a good web-browser
Date: Mon, 13 Jul 2009 03:18:43 -0400 [thread overview]
Message-ID: <8548A4DA-8700-4A7B-AAE2-37A3CE030D7A@raeburn.org> (raw)
In-Reply-To: <jwvk52fc79d.fsf-monnier+emacs@gnu.org>
On Jul 11, 2009, at 16:24, Stefan Monnier wrote:
> The Emacs/W3 way is sadly unworkable because of the
> amount of effort this requires (compounded by the performance
> limitations of Elisp).
Guile has had some performance work done lately, and has a bytecode
engine of its own; no JIT compilation to machine code yet, but people
are certainly keeping it in mind. I don't know how the ECMAScript
performance compares to a random browser's Javascript engine
currently, and (according to http://wingolog.org/archives/2009/02/22/ecmascript-for-guile
though maybe things have changed) I guess Andy Wingo doesn't
either. But the ECMAScript support is a second language reader for
the compiler, so when the Scheme compilation and optimization support
improves, so should the ECMAScript support.
Ken
next prev parent reply other threads:[~2009-07-13 7:18 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 20:11 Why Emacs should have a good web-browser Fernando
2009-07-08 20:54 ` Chong Yidong
2009-07-08 21:55 ` joakim
2009-07-08 22:42 ` Lennart Borgman
2009-08-13 22:54 ` Daniel Colascione
2009-07-08 22:55 ` Chong Yidong
2009-07-08 22:59 ` Lennart Borgman
2009-07-08 23:05 ` Davis Herring
2009-07-09 0:05 ` joakim
2009-07-09 12:36 ` Jason Rumney
2009-07-09 14:25 ` joakim
2009-07-09 16:01 ` Chong Yidong
2009-07-09 17:39 ` joakim
2009-07-09 22:19 ` Richard Stallman
2009-07-08 20:58 ` Richard Riley
2009-07-09 21:12 ` Paul R
2009-07-11 20:24 ` Stefan Monnier
2009-07-12 11:01 ` Robert D. Crawford
2009-07-13 7:18 ` Ken Raeburn [this message]
2009-07-17 15:59 ` Paul R
2009-07-18 1:29 ` Miles Bader
2009-07-21 9:18 ` Paul R
2009-07-21 15:52 ` Stefan Monnier
2009-07-21 16:31 ` Miles Bader
2009-07-21 17:25 ` Thomas Lord
2009-07-22 9:23 ` Paul R
2009-07-21 16:52 ` David Reitter
2009-07-21 20:34 ` Chong Yidong
2009-07-21 17:13 ` Thomas Lord
2009-07-21 18:21 ` Adam Wołk
2009-07-21 19:01 ` Lennart Borgman
2009-07-21 19:26 ` Adam Wołk
2009-07-21 19:33 ` Lennart Borgman
2009-07-21 19:47 ` Adam Wołk
2009-07-21 20:02 ` Robert D. Crawford
2009-07-21 20:08 ` Lennart Borgman
2009-07-21 20:37 ` Robert D. Crawford
2009-07-21 20:24 ` Adam Wołk
2009-07-21 21:27 ` Robert D. Crawford
2009-07-21 21:36 ` T.V. Raman
2009-07-21 22:14 ` Robert D. Crawford
2009-07-21 21:48 ` Adam Wołk
2009-07-21 22:24 ` Robert D. Crawford
2009-07-22 10:33 ` Tassilo Horn
2009-07-22 9:12 ` Paul R
2009-07-22 14:47 ` Stefan Monnier
[not found] ` <fxezoucvx5x8i57cbqUYAxe124vaj_firegpg@mail.gmail.com>
2009-07-21 22:09 ` Stephen Eilert
2009-07-21 23:05 ` Chong Yidong
2009-07-22 17:40 ` Stephen Eilert
2009-07-22 18:07 ` Chong Yidong
2009-08-30 18:22 ` joakim
2009-09-02 9:58 ` martin rudalics
2009-09-02 12:00 ` joakim
2009-09-12 19:03 ` Deniz Dogan
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=8548A4DA-8700-4A7B-AAE2-37A3CE030D7A@raeburn.org \
--to=raeburn@raeburn.org \
--cc=emacs-devel@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.