What about adopting Hemlock?
What about adopting Hemlock?
Posted May 30, 2020 17:24 UTC (Sat) by jgfenix (guest, #113371)Parent article: Making Emacs popular again
Posted May 30, 2020 18:34 UTC (Sat)
by jem (subscriber, #24231)
[Link] (1 responses)
If you are suggesting the GNU Emacs project should abandon their current code base and adopt Hemlock instead, what problem would that solve? Would it solve the usability or the not-so-sleek look of GNU Emacs mentioned in the article? What about the millions of lines of Elisp code? Would Elisp compatibility be possible to implement in Hemlock? Emacs Lisp is not going away ever.
The port of GNU Emacs to use Guile instead of the built-in Lisp implementation has failed so far, but not because Scheme is a weak language or Guile a bad implementation of Scheme. The problem with Guile Emacs has to do with the difficulty of integrating Guile with Emacs and getting the final bits of Elisp compatibility to work, getting the editor to start up fast enough, etc.
The idea with Guile Emacs is not to replace Emacs Lisp with Scheme (not initially, anyway), but to use a better (faster), and more decoupled implementation. Interest in Guile Emacs has slowed down because people are asking the rhetorical question "what problem does it solve?"
Posted May 31, 2020 2:12 UTC (Sun)
by pabs (subscriber, #43278)
[Link]
What about adopting Hemlock?
What about adopting Hemlock?