News for hackers. Stuff that matters.
Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy by nine_k on Friday August 06, 2021 @04:42PM (#28092521)
If only VSCode had sane buffer control, and the idea of buffers.

I use VSCode with Emacs key bindings for certain development. The lack of uniformity inconveniences me a lot.

But indeed, VSCode is the closest thing to Emacs in its spirit.

Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy by krylon on Friday August 06, 2021 @07:04PM (#28093787)
I haven't given them a close look, but there is a project called "zile" that - AFAIU - aims to create an emacs-like editor using Lua instead of Lisp. Which sounds amazing to me.

Also, there's another project to replace emacs' lisp interpreter / bytecode VM with GNU Guile, which started out as an embeddable Scheme interpreter, but apparently these days it is a JIT compiler that supports Scheme, Javascript, and elisp. Which means Guile-Emacs could absorb all of that elisp code without a problem, probably make it run faster, too, but also open the door for people that don't feel comfortable with elisp. More importantly, maybe, this project could bring people from different language communities together.

Again, I have not spent much time looking into the project, so consider all of what I'm writing hearsay. But things are happening.

Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy by Koshkin on Friday August 06, 2021 @04:51PM (#28092601)
Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy by iLemming on Friday August 06, 2021 @06:24PM (#28093465)
No, it's not. It's nothing like Lisp and will never be, simply because it misses the biggest (arguably most important) feature of Lisp - homoiconicity.

But sure, if you squint your eyes - pretty much every single modern programming language would be "like a Lisp" Why? Because there's not a single programming language in use today that was not influenced by ideas first pioneered in Lisp.