RE: jde considered harmful
Andy Piper writes:
> This must definitely be an Xemacs
> problem.
Well, probably - although often these things
turn out to be due to the different architectures
of XEmacs and Emacs. The key here is to find out
what the problem actually is.
For instance it takes roughly 11 seconds to
load JDE on my PIII 850 and 5 seconds to load
and fontify a 1500 line Java file. I suspect
that the original problem is not so much
the speed of JDE but just the time it takes
JDE to load on XEmacs.
This is not my impression. He mentioned that it took
about 2 seconds to fontify and then more than 20 seconds
to bovinate. He seemed to be complaining about
the latter. He did not mention the JDEE load time
at all.
The JDEE itself does take a long time to load,
which is not surprising considering the size
of the application. The JDEE includes
23 Lisp packages and directly requires about
13 external Lisp packages, some of them quite
large in themselves, e.g., semantic.
- Paul
This is on a cygwin
compiled XEmacs which is known to be slower
than a natively compiled XEmacs.
> I tried Xemacs and abandonned it a long
> time ago because it thought that a file
> loaded through a soft link was different
> from the same file loaded along the
> normal path and because the the debugger
> (JDEbug) took forever.
I believe these problems have been fixed.
Certainly these things work well enough for me.
andy