Live data from Hacker News

Emacs is Dead (2010)

tkf.github.io

1–10 of 115 posts

Re: Emacs is Dead (2010)

#2
re: the social value of emacs-lisp parsers/code-completion etc, perhaps someone could supply an API where other programs can query a headless emacs runtime. I defer to the author's experience when he says that emacs is a poor runtime for simultaneous editing + compute, but perhaps it's acceptable for compute-only (and this separate-process approach could in theory improve interactivity for the emacs editor as well).

My emacs at times can't keep up with my typing. But I love what it does for me. The lack of threading is a huge headache for elisp developers - they have to resort to manual cooperative-task-slicing hacks.

Re: Emacs is Dead (2010)

#3
The biggest problem being Emacs isn't just a text editor. If it were, most if not all of these problems would have been resolved already. It's very hard to make repairs to a working bridge while in service and carrying rush-hour traffic. There's just so much predictability counted on by everyone who uses it, there are really no simple solutions.

I have to say though, external module(s) may be the way to go about it.

For the curious :

http://www.emacswiki.org/emacs/TrampMode

Re: Emacs is Dead (2010)

#4
This is actually really interesting from a vim user's perspective. We've long sought after an extension language as good as emacs lisp and finally now have gotten the news that vim plans to eventually phase out vimscript in favor of Python. The future looks good!

Re: Emacs is Dead (2010)

#5
I don't believe that Emacs is dead at all. Actually, most of the problems (multithreading, libraries, file I/O) raised by this article can be solved by replacing Emacs Lisp backend with Guile, which is an active and promising project [1,2]. As for Emacs philosophy, it might even survive Emacs (in the hypothetical situation where Emacs dies) if a project such as Emacsy (the second one presented in [1]) takes off.

[1] https://lists.gnu.org/archive/html/guile-user/2013-05/msg000...

[2] https://www.google-melange.com/gsoc/proposal/review/google/g...

Re: Emacs is Dead (2010)

#6
This should have been titled "The death of the Emacs Philosophy", although I am not sure what that is exactly. Emacs will hang on for a litte while.

Re: Emacs is Dead (2010)

#7

This is actually really interesting from a vim user's perspective. We've long sought after an extension language as good as emacs lisp and finally now have gotten the news that vim plans to eventually phase out vimscript in favor of Python. The future looks good!

Really? That would be cool. Can you point me to a thread or something where I can read about these developments?

Re: Emacs is Dead (2010)

#8

This is actually really interesting from a vim user's perspective. We've long sought after an extension language as good as emacs lisp and finally now have gotten the news that vim plans to eventually phase out vimscript in favor of Python. The future looks good!

As a vim user it doesn't make sense that you didn't already know vim was scriptable with multiple other languages (e.g. perl, ruby, tcl, python ...) already for a long time.

As a vim user, emacs lisp is bad. A proper lisp would be more worthwhile.

Re: Emacs is Dead (2010)

#9
post #7

This is actually really interesting from a vim user's perspective. We've long sought after an extension language as good as emacs lisp and finally now have gotten the news that vim plans to eventually phase out vimscript in favor of Python. The future looks good!

Really? That would be cool. Can you point me to a thread or something where I can read about these developments?

For vim scripting with Python: http://www.tummy.com/presentations/vimpython-20070225/

Re: Emacs is Dead (2010)

#10

This is actually really interesting from a vim user's perspective. We've long sought after an extension language as good as emacs lisp and finally now have gotten the news that vim plans to eventually phase out vimscript in favor of Python. The future looks good!

I think you have misinterpreted something. There have been a lot of Vim patches recently that are dramatically improving the long-existing Python scripting support in preparation for the upcoming Vim 7.4 release. But Bram has not said anything about "phasing out" VimScript. The two languages will continue to coexist (along with the handful of others that are also supported). There is far too much investment in VimScript, however flawed it may be, to actually deprecate or remove it.
Post reply on HN