4 ms·
I've been pondering this for a while. I think you could have a JS-based editor that approaches or achieves what emacs offers, but I haven't encountered it. One
by Jtsummers 6y ago
I've been pondering this for a while. I think you could have a JS-based editor that approaches or achieves what emacs offers, but I haven't encountered it. One useful thing about emacs and elisp is that lisp is one of the primary modes of interaction for users, whereas (IME) many JS-based editors seem to hide JavaScript from you to some extent.
Not in the sense that it's not there, or that there's a second language that the JS interprets. But when you open emacs without specifying a file to open you are dropped into a buffer called *scratch* which lets you directly execute elisp code. It really is a central part of the experience of using emacs. Similarly, your configuration file(s) are written in elisp, versus often a subset of JavaScript (perhaps JSON) used in JavaScript-based editors. And you're not just supplying configuration data, but extending the program.
And then there's completeness. While emacs has parts written in C, that portion really exists to enable elisp. Essentially every capability of the editor is directly reachable through lisp. The same doesn't seem (or at least feel) true of JavaScript-based editors I've tried. In those, it often feels more like the creators have selected a portion of the internals to expose to users, but it's more the minimal amount needed rather than the maximal amount possible that emacs strives for.
EDIT: I've finally figured out how to insert an asterisk around a word on HN without needing spaces. Is this documented anywhere? Just use double asterisks on either end like
**foo**
*foo*
Turns out this is in the FAQ, it's been a while since I looked at the formatting part of that so I guess it changed since 10 years or so ago or I'd forgotten.
- adamnew123456 6y agoThe Advent of Computing [1] podcast recently put out their episode 47 which I think provides a sort-of explanation of this line of thinking. The short answer is that the context in which Emacs was originally developed (a contemporary of Unix, and not Unix itself, which was something I wasn't aware of before) emphasized user power and lack of restriction to a much greater degree than much of the current computing landscape does. Why would you lock users or developers into a fixed, defined plugin API when you could write the application in such a way that they have access to whatever they need? Excluding maybe NodeJS, most of the Javascript you encounter is going to be executed by a browser which has a whole ton of sandboxing and mitigation mechanisms to prevent the big bad web from abusing your computer. I don't blame it for working that way given how few trustworthy (I mean really trustworthy, as in "free range within $HOME") actors exist on the web these days, but one wonders how far we could take the web ecosystem if we tossed the idea of granting special access through WebGL or WebUSB and just gave the browser full access to calling C or executing processes on your system. Don't get me wrong - it would be a security nightmare, but there's a cost to trying to guarantee security through mechanism rather than trust. [1] https://adventofcomputing.libsyn.com/episode-47-its-open-computing https://adventofcomputing.libsyn.com/episode-47-its-open-com...
- kazinator 6y ago> While emacs has parts written in C, that portion really exists to enable elisp. You should do a line count; GNU Emacs has more than 250,000 lines of C.
- Jtsummers 6y agoThat remark wasn't about how much is written in C, but what is done with the portion that is written in C (in contrast to the popular JS-based editors). In emacs, the portions in C appear to mostly be (no desire to produce an actual breakdown) there for: 1. Handling system calls for IO, networking, display 2. Implementing the elisp language itself 3. Implementing some things so they're faster than raw elisp And the preference seems to be to expose, to the greatest extent possible, functionality to the elisp users, even if it's actually implemented in C. This is in contrast to the popular JS-based editors which seem to be more interested in a more controlled/limited exposure of functionality to users.