sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:
I don't want to be splitting hairs too much, but most of the
I see *is* related to Elisp. Redisplay is plenty fast for me, and
buffer operations as well. Stuff like func-menu, on the other hand,
is causing noticeable delays as well as things like jumping to a
non-displayed group in Gnus (... and quite a few other things in
Gnus.) No doubt improvements are possible in areas other than Elisp.
However, Elisp *is* a main source of slowness.
While I can't really say whether elisp is the main source of slowness
or not, I think having a much faster lisp engine would be a major win.
I recall many (some?) pieces of code were moved from C to Lisp back
to C because the lisp version was too slow.
I think it would be nice if almost everything were in Lisp, with C
being just the bare minimum. That would help out portability of xemacs
Maybe a lisp engine like CLISP would be fast enough. It's reasonably
small and pretty fast for being a byte-code implementation.