On Fri, 06 Dec 2002, [EMAIL PROTECTED] wrote: > > If I could, then I would be able to make really powerful things > without lisp, in plain java. But then I may as well switch to > jedit altogether ;-) I won't, just teasing!
This is probably the reason that Emacs seems like a neanderthal to the "modern" editor. The JVM is the rage, but Emacs is written in a virtual machine which isn't the rage. Making those two able to communicate is an issue the Paul is solving quite well, but the solution isn't the "sexy" java one. Its an Elisp one. Its too bad that alot of today's great java developers never turned to Emacs for their environment. I think Paul has shown that Emacs can, should and will keep up with almost any new technology. If we had even more java guys interested in Emacs, it would help a bunch. But, then, this is why your idea seems so appealing. Having an Elisp|Java interface would mean that java and elisp guys could partition what they are working on to the defined interfaces. -- Galen Boyer
