Conversation

Notices

1. Embed this notice
   hajovonta (hajovonta@mastodon.online)'s status on Monday, 14-Apr-2025 21:11:52 JST hajovonta

   • Glitzersachen.de

   @glitzersachen
   My point is, it's relatively easy to bridge the gap between two Lisps and I gave a practical example.

   So as stupid this decision was as is, it could prevent people for a limited time only.

   • Embed this notice
     Alfred M. Szmidt (amszmidt@mastodon.social)'s status on Monday, 14-Apr-2025 21:11:51 JST Alfred M. Szmidt

     in reply to

     • Glitzersachen.de

     @hajovonta @glitzersachen It isn't a "stupid decision", or rooted the "middle ages". Emacs Lisp and Common Lisp come from two separate traditions, and have different goals.

     It is also not a single persons "personal experience/taste/idiosyncrasies" -- lets stop with this charade.

   • Embed this notice
     Alfred M. Szmidt (amszmidt@mastodon.social)'s status on Monday, 14-Apr-2025 21:36:23 JST Alfred M. Szmidt

     in reply to

     • Glitzersachen.de

     @hajovonta I don't think it is much about old stories, Emacs Lisp and Common Lisp are two different languages, with different goals .. it is fine that they are different.

     The big issue with "becoming CL" is that now .. you're stuck, and cannot evolve the language at all (not to mention all the breakage).

     Does it suck that I cannot use a nice Python library in Emacs Lisp? Yes ... and nobody is trying to make Emacs lisp into Python, and there are many nice things there too...

     @glitzersachen

   • Embed this notice
     hajovonta (hajovonta@mastodon.online)'s status on Monday, 14-Apr-2025 21:36:24 JST hajovonta

     in reply to

     • Glitzersachen.de
     • Alfred M. Szmidt

     @amszmidt
     OK, sorry. I admit I know little about the old stories.

     @glitzersachen

   • Embed this notice
     Alfred M. Szmidt (amszmidt@mastodon.social)'s status on Monday, 14-Apr-2025 21:40:16 JST Alfred M. Szmidt

     in reply to

     • Glitzersachen.de

     @hajovonta I was thinking more or the normal meaning of the word, but yeah .. it is not very different from using Common Lisp via SBCL/ECL/... in Emacs lisp.

     @glitzersachen

   • Embed this notice
     hajovonta (hajovonta@mastodon.online)'s status on Monday, 14-Apr-2025 21:40:17 JST hajovonta

     in reply to

     • Glitzersachen.de
     • Alfred M. Szmidt

     @amszmidt
     "Does it suck that I cannot use a nice Python library in Emacs Lisp? Yes ... and nobody is trying to make Emacs lisp into Python"

     well, you can, with some limitations, and there are people who try to achieve this.

     @glitzersachen