3 ms·
Can it be true? Can we finally write our Emacs plugins in Scheme or Common Lisp, and have them work? Wait, then we'll have 2 GCs fighting over data. Dang it. W
by qwertyuiop924 10y ago
Can it be true? Can we finally write our Emacs plugins in Scheme or Common Lisp, and have them work?
Wait, then we'll have 2 GCs fighting over data. Dang it. We were almost free!
Seriously, though, I do have some concerns. If the new Plugin API becomes widely used enough, elisp may become a second-class citizen in the ecosystem, which would mean that emacs would no longer be easily programmable. That would be bad.
- zitterbewegung 10y agoConsidering the amount of code written out there for emacs making the original scripting language a second class citizen would be an enormous undertaking. Most other languages have taken years to convince people to upgrade (Python, Perl.. ) . I really don't think having elisp as a second class citizen would happen anytime soon.
- sn9 10y agoCouldn't you try compiling OCaml or another language to Emacs lisp bytecode [0]? [0] https://en.wikipedia.org/wiki/Emacs_Lisp#Source_code https://en.wikipedia.org/wiki/Emacs_Lisp#Source_code
- wcummings 10y agoExactly, the elisp monoculture is a feature not a bug.
- qwertyuiop924 10y agoWell, so long as extensions have to pass elisp data, it's okay-ish.