4 ms·

> the system language is awkward (no namespaces, dynamic scoping by default, ...) RMS's dislike of Common Lisp really caused a colossal amount of damage. Imag

by zeveb 5y ago

> the system language is awkward (no namespaces, dynamic scoping by default, ...) RMS's dislike of Common Lisp really caused a colossal amount of damage. Imagine an Emacs written in Common Lisp instead of Emacs Lisp, with decades and decades of improvements. Having written a reasonable amount of software in both, Common Lisp Emacs would be very, very preferable, in part for the reasons you list and in part for others (e.g. a full-fledged, built in object system and improved extensibility).

sreevisakh 5y ago
That may be what nyxt browser is trying to do. The author claims that nyxt could be extended to be anything, including an alternative for emacs. [1] https://nyxt.atlas.engineer/article/why-building-nyxt-instead-of-an-emacs-package.org https://nyxt.atlas.engineer/article/why-building-nyxt-instea...
wrs 5y ago
There has been some work on that over the decades (but of course not enough momentum): https://phemlock.common-lisp.dev/ https://phemlock.common-lisp.dev/
deng 5y ago
> RMS's dislike of Common Lisp really caused a colossal amount of damage. Imagine an Emacs written in Common Lisp instead of Emacs Lisp, with decades and decades of improvements. If Emacs were written in Common Lisp, only people on big mainframes would have been able to use it in 1985, and it probably wouldn't have become popular in the first place. Also, implementing Common Lisp would have taken much longer. RMS has said that his main goal with his LISP dialect was to keep the programming language as small and performant as possible, since at that time, machines had maybe 1MB of RAM (if you were lucky) and no virtual memory. This is why for instance he decided against lexical scoping (and still, Emacs was known back then as "eight megabytes and constantly swapping").
- lispm 5y ago
  IIRC, Coral Common Lisp ran on a Mac Plus, which had 1 MB RAM. It included an editor.
schemingguild 5y ago
I'm very interested in guile-emacs, not because I think it'll replace main emacs, but I do think it'd be really neat to have my config in a 'cleaner' lisp like scheme, a clojure like language, lokke[0], or even python[1] [0]: https://github.com/lokke-org/lokke https://github.com/lokke-org/lokke [1]: https://gitlab.com/python-on-guile/python-on-guile https://gitlab.com/python-on-guile/python-on-guile

by zeveb 5y ago

sreevisakh 5y ago

That may be what nyxt browser is trying to do. The author claims that nyxt could be extended to be anything, including an alternative for emacs. [1] https://nyxt.atlas.engineer/article/why-building-nyxt-instead-of-an-emacs-package.org https://nyxt.atlas.engineer/article/why-building-nyxt-instea...

wrs 5y ago

There has been some work on that over the decades (but of course not enough momentum): https://phemlock.common-lisp.dev/ https://phemlock.common-lisp.dev/

deng 5y ago

> RMS's dislike of Common Lisp really caused a colossal amount of damage. Imagine an Emacs written in Common Lisp instead of Emacs Lisp, with decades and decades of improvements. If Emacs were written in Common Lisp, only people on big mainframes would have been able to use it in 1985, and it probably wouldn't have become popular in the first place. Also, implementing Common Lisp would have taken much longer. RMS has said that his main goal with his LISP dialect was to keep the programming language as small and performant as possible, since at that time, machines had maybe 1MB of RAM (if you were lucky) and no virtual memory. This is why for instance he decided against lexical scoping (and still, Emacs was known back then as "eight megabytes and constantly swapping").

lispm 5y ago
IIRC, Coral Common Lisp ran on a Mac Plus, which had 1 MB RAM. It included an editor.

schemingguild 5y ago

I'm very interested in guile-emacs, not because I think it'll replace main emacs, but I do think it'd be really neat to have my config in a 'cleaner' lisp like scheme, a clojure like language, lokke[0], or even python[1] [0]: https://github.com/lokke-org/lokke https://github.com/lokke-org/lokke [1]: https://gitlab.com/python-on-guile/python-on-guile https://gitlab.com/python-on-guile/python-on-guile