Still waiting for Guile Emacs.
guix package -i guile-emacsI hope it does. The original vi's lisp mode is something I have only seen traditional vi implement thus far, and it's pretty nice.
Vim + paredit inside of tmux, with a proper REPL in another pane / window is a great workflow. Of course this requires some more plugins to Vim, but for the most part sending commands through tmux is pretty lightweight.
[0] https://bitbucket.org/kovisoft/slimv [1] http://www.nongnu.org/geiser/
When editing lisp in the original vi's Lisp mode, ( and ) operate over sexprs, { and } don't stop at atoms, moving you to the next sexpr, [[ and ]] skip to the next sexpr at top level, and if you set autoindent, your code is indented correctly for lisp.
Combined with vi's other operators, this is pretty good, although by no means as good as actual paredit.
With that kind of number, you're pretty much guaranteed some elisp is going to stick around forever (especially considering Emacs' glacial [but improving!] rate of change).
So yeah, it's not so much the Elisp in the Emacs source that's the problem, it's how do the maintainers switch to maintaining Elisp inside of the Guile project (up until now, Elisp was maintained as a language alongside Emacs). At the very least, this is how I understand it.
Yes, there is no way Emacs will get rid of elisp. That's why Guile Emacs includes writing an elisp frontend for Guile. (There is also a Frontend for ECMAScript and an experimental one for Lua)
Seems like it's not to far from being stable (if not perfect performance wise).