3 ms·
I've been down this rabbit hole, to the level of reading disassembled bytecode to optimize preformance. Elisp is alright for what it is, but Emacs itself contai
by LanternLight83 3y ago
I've been down this rabbit hole, to the level of reading disassembled bytecode to optimize preformance. Elisp is alright for what it is, but Emacs itself contains so many hacks and subsystems at the C level that elisp isn't allowed the comprehensive level of access that it would need to make m̶e̶ ̶h̶a̶p̶p̶y̶ highly performant extensions.
To be clear, these limitations in reasonable package scope come with positive trade-offs in the broader ecosystem such as promoting stability, inter-operability within emacs, and the insulatory disuse of FFI. I just feel like Emacs promised me I could do anything with elisp, and then denied me the low-level control that a lisp like Guile or Common Lisp is capable of. Helix does this better by not h̶a̶v̶i̶n̶g̶ ̶e̶x̶t̶e̶n̶s̶i̶o̶n̶s̶ making any promises.