I think your arguments are fair, well, for the most part of your sentiment anyway. I do use CIDER almost daily and have not experienced critical memory leaks an

I think your arguments are fair, well, for the most part of your sentiment anyway. I do use CIDER almost daily and have not experienced critical memory leaks and I don't feel like I'm fighting Emacs warts all the time, although of course, it would be silly of me to deny the fact that Emacs indeed has many. Of course, Clojure is far more nicer language than elisp, I personally like it perhaps even more than CL, but that might be only because I lack extensive practice of CL. I really wish core Emacs developers had more exposure to Clojure, maybe then we would've gotten some niceties borrowed from it. Imagine if we could have clojure-like maps in elisp? I am hoping for the day when a practical alternative for Emacs comes around, yet the occasional bleeps that appear on the event horizon are too far from dethroning Emacs anytime soon. Lem seems to have good foundations, but I'm not sure if it will ever succeed to the point of being a possible complete replacement. The Easel project looks interesting, but it's still too early to say if it will ever grow out of its incubation https://github.com/phronmophobic/easel https://github.com/phronmophobic/easel. Light Table also looked great in theory, in practice - it never became a thing. Sadly (or not) Emacs remains ultrapractical. The only and the main reason why I still use it - it works, yes, it's not ideal yet it does get the job done. That's perhaps the same argument an average VSCode user would make, however without a clue what it is like to be able to manipulate virtually any aspect of your editing environment via Lisp REPL.