unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Michael Reilly <pmr@pajato.com>
To: Thomas Lord <lord@emf.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Very interesting analysis of "the state of Emacs"
Date: Tue, 29 Apr 2008 03:26:46 -0400	[thread overview]
Message-ID: <4816CDB6.6000006@pajato.com> (raw)
In-Reply-To: <481693C3.70901@emf.net>

Thomas Lord wrote:
 > Emacs developers might find value in reading this analysis by Steve 
Yegge:
 >
 > 
http://steve-yegge.blogspot.com/2008/04/xemacs-is-dead-long-live-xemacs.html 


This is a terrific read.  It captures the top two items on my
Gnu/Emacs wish list: first class browsing and multi-threading.

If ever I prayed for the success of an Emacs library coding effort, it
would definitely have been for w3 mode by William Perry.  But it
clearly was a very hard problem.  I've seen signs of improvement in
graphics rendering over the years that makes me believe a decent
browsing experience can be had.  But it's not there yet.

The other hard problem is multi-tasking in the Emacs Lisp engine.
RMS once left me with the impression that this was virtually
intractable, especially if one wanted to have existing Elisp code base
compatibility, a reasonable thing to want.

So I see the best bet for achieving the holy grail of fast browsing,
emacs editing and multi-threading will be via embedding Emacs into the
browser such that every tab/screen IS an Emacs buffer/frame, rendered
in one of some small number (two?) of easily selectable alternatives.
Admittedly, how multi-threading fits into that model is blurry at
best.

But then Steve's point about this solution being fraught with ugliness
if left in the hands of the Mozilla foundation is extremely well
taken.

So all in all, suggesting that the XEmacs folks be encouraged to
pursue these kinds of hard problems under the Gnu/Emacs umbrella is a 
great suggestion, IMHO.

-pmr




  reply	other threads:[~2008-04-29  7:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29  3:19 Very interesting analysis of "the state of Emacs" Thomas Lord
2008-04-29  7:26 ` Paul Michael Reilly [this message]
2008-04-29 23:17   ` Richard M Stallman
2008-04-30  0:14     ` Thomas Lord
2008-04-30  2:21     ` Stephen Eilert
2008-04-30  3:20       ` dhruva
2008-04-30 22:00         ` Richard M Stallman
2008-04-30 22:49           ` David Hansen
2008-04-30 23:46             ` Thomas Lord
2008-05-01  7:30               ` tomas
2008-05-01  4:23             ` Jonathan Rockway
2008-05-01  6:31               ` David Hansen
2008-05-01  6:42               ` Miles Bader
2008-05-01 18:59                 ` Jonathan Rockway
2008-05-02 15:36                 ` Stefan Monnier
2008-05-02 16:50                   ` CEDET and threads (was Re: Very interesting analysis of "the state of Emacs") Eric M. Ludlam
2008-05-03  8:09                   ` Very interesting analysis of "the state of Emacs" Richard M Stallman
2008-05-03 19:24                     ` Stefan Monnier
2008-05-04  9:37                       ` Richard M Stallman
2008-05-04 23:23                         ` buffer transactions (was Re: Very interesting analysis of "the state of Emacs") Nic
2008-05-05 15:14                           ` Richard M Stallman
2008-04-30  5:12       ` Very interesting analysis of "the state of Emacs" Miles Bader
2008-04-30 14:06         ` David Kastrup
2008-04-30 15:08         ` Tom Tromey
2008-05-15  6:21           ` ERC disconnects when blocked too long (was: Very interesting analysis of "the state of Emacs") Michael Olson
2008-04-30 16:08         ` Very interesting analysis of "the state of Emacs" Thomas Lord
2008-04-30  6:24       ` Paul Michael Reilly
2008-04-30 14:12       ` Mathias Dahl
2008-04-30 22:01       ` Richard M Stallman
2008-04-30 22:56         ` Thomas Lord

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/emacs/

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

  git send-email \
    --in-reply-to=4816CDB6.6000006@pajato.com \
    --to=pmr@pajato.com \
    --cc=emacs-devel@gnu.org \
    --cc=lord@emf.net \
    /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 public inbox

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

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).