Get the latest tech news
Why Does Elisp Suck
(See also EmacsLispLimitations, SchemeAndLisp) I’m a long-time Emacs user who is new to the under-the-hood side of things. I recently started learning EmacsLisp and writing my own Emacs extensions.
I know that the design of Emacs evolved in the time when a programmer only had access to a single terminal session to a computer, thus becoming in effect the world’s first Integrated Development Environment so a user could meet all their needs without dropping in and out of their primary application: the editor. I’d really like to be able to use python for that, and maybe one day seamlessly interface Emacs with .NET runtime (if nothing else, just for introspection data you can get for free in .NET / Java, it’s really kinda necessary when writing in environment that consist almost 100% of library functions and classes) EmacsLisp(as it is today) really sucks. Not just threads and other low-level tools needed for synchronization or mutual exclusion (I’d even prefer that those be hidden from sight), but a thought-through system based on either Actors model, or Concurrent C / Ada, or maybe something else, genuinely new?
Or read this on Hacker News