4 ms·
No, we couldn't have had GuileEmacs for a long time since the compatibility layer with Elisp wasn't complete - that meant that not all Existing Emacs packages c
by pkd 10y ago
No, we couldn't have had GuileEmacs for a long time since the compatibility layer with Elisp wasn't complete - that meant that not all Existing Emacs packages could be used as is with a GuileEmacs. This release specifically addresses that and I am sure that now there will be serious effort to bring about a "stable" GuileEmacs release.
- rurban 10y agoThe missing compatibility layer is peanuts compared to the string performance problems underneath. This was my important question, which is not answered in the release announcement. You could force guile on everybody, just as e.g. perl5 did with their Test2 replacement, but not everybody will be happy with a 20% performance hit in the real world, and esp. when telling nobody about it. This would be pure marketing shit.