How difficult is it to write an "Emacs Lisp" interpreter in a foreign framwork like neovim? Wouldn't this basically convert any IDE into Emacs if the user wants it?
I mean, I know elisp is not the most efficient of Lisp compilers but doing so for a new IDE opens the door for all available codes and plugins people have written for emacs throughout the years.
I think a huge compatibility layer would also needs to be part of that. Most IDEs probably use a completely different vocabulary and set of concepts than Emacs, starting with buffers and mode lines and minibuffers and modes.
> Wouldn't this basically convert any IDE into Emacs if the user wants it?
Emacs Lisp is only part of the equation. You need the all of the programmability that implements 90% of Emacs in Lisp (all of the standard library functions, the display engine, etc).
I mean, I know elisp is not the most efficient of Lisp compilers but doing so for a new IDE opens the door for all available codes and plugins people have written for emacs throughout the years.