12 ms·
I like Clojure and all, but this is just ... silly. First, 100% elisp compatibility is the no-exceptions requirement. Clojure doesn't have freakin' car and cdd
by spopejoy 12y ago
I like Clojure and all, but this is just ... silly.
First, 100% elisp compatibility is the no-exceptions requirement. Clojure doesn't have freakin' car and cddadr, not to mention the significant syntax differences. LISP weenies don't even think Clojure is a proper LISP, whereas elisp comes close to a functional subset of CL.
Next, the JVM. There's lots to like about the JVM, but it's not particularly well-suited for embedding in a text editor, which is why JEdit hasn't taken over the world. It's also not compact. The last thing Emacs needs is batteries-included Java being loaded up.
Multithreading: guile can do it, and emacs doesn't need industrial strength or crazy map-reduce. We just need emacs not to hang whilst TRAMP calls 'ls' on a remote server. Freaking timesharing would work, modern machines are more than fast enough with one thread.
Putting clojure in emacs would basically be starting over, on the wrong foot. I'd rather rebuild on GHC.