Emacs is unique and I'd like to preserve that.
>What's wrong with spreading all this to other spaces, and letting other people learn about them, making them more accessible?
Because the philosophy of Emacs and the computing tradition it grew out of is fundamentally at odds with those other spaces. Everything being in one dynamic language is a huge and intrinsic part of that tradition.
I suppose could you write an Emacs entirely in javascript if you wanted to, if you followed the same software philosophy. But personally I think Javascript is such an inelegant language that a lot of the power of the idea would be lost even in that case.
I don't think that's true at all. Emacs is a lisp-machine, but that's just the means, an implementation-detail, not the culture and the aim. Every shell, web browsers, any REPL is pretty much the same as Emacs, just in a different flavor. The culture I'm talking about is to have a customizable tool & workspace. Something that adapts to you, a canvas where only your time and imagination is the limit. Limiting Emacs to being "just" lisp, is doing it a disservice.
Browsers are nothing like Emacs in design philosophy(except Nyxt, which gets close, but falls a bit short due to intrinsically having to deal with a bunch of JS; an excellent example of my point, come to think of it).
Take Firefox for example. It has extensions, but they're intrinsically limited by the fact that they're sandboxed and can only interact with the browser through a limited API. And yes, you could certainly extend it arbitrary by changing the C++/Rust/whatever code and recompiling it. But it's not designed to be extended that way by users.
In emacs, the configuration is really just patches applied to the code at runtime. There fundamentally is nothing you can't do through the configuration.
But why Lisp you say? Precisely because Lisp is a dynamic meta-programming language, which is the ideal paradigm for this. It can be molded to be a highly abstracted configuration language without losing the ability to run arbitrary code. You get all the upside of JSON, YAML, XML and other configuration languages with none of the downside of being limited in what you can do.
Adding javascript to the mix just complicates this simple and elegant model. You gain nothing in extensibility, and will probably lose quite a lot unless you take extreme effort to avoid it through clever design.
That's design, a choice. It used to be different in old Firefox, and other browsers are different in that aspect even today. But to be fair, I mainly meant the page-context, not the application-context. Most normal web browser support userscript, bookmarklets and debugging some way or another. Or should I say, still. Because this is a bit in decline. And if you take something like web- or electron-apps, the page-context becomes the app itself. All just a matter of implementation and architecture.
> There fundamentally is nothing you can't do through the configuration.
You can't patch the C-core, can you? Another necessary implementation-detail.
> Precisely because Lisp is a dynamic meta-programming language, which is the ideal paradigm for this.
It was ideal when Emacs was created. Today, we have many alternatives.
> You gain nothing in extensibility,
Except more ability, more heritage, more users... At the end, it's all a matter of managing the tradeoffs, the implementation-details.
The C core contains low-level things or performance-sensitive things that one really doesn't want to patch. Nevertheless, lots of things in the C core are configurable and extendable through hooks.
> Except more ability, more heritage, more users... At the end, it's all a matter of managing the tradeoffs, the implementation-details.
Regarding heritage, you can't get more than Enacs has, which was around when GUI didn't even exist yet.
Users who are put off by the choice of configuration language are unlikely to be productive extension writers.
Something as simple as getting advice for solving a problem on web forums would also be affected by the dichotomy. I think that might be worse for newbies.
Still, I think it's fine to run the experiment, and see if that is what people want.
I can almost see the argument for browser, but we left user customization as the default in browsers a long long time ago.
To make my point a bit more concrete, the culture of lisp-machines was that the user was in full control. Curious what will happen if you type something? You can literally lookup what will happen on any keystroke or button press. Curious what code runs for a function? Odds are high that you can jump into the code for any feature and edit it on the fly. Yes, there are some native code sections that you can't do this for, but the vast majority is not that.
Im curious why someone would use emacs if they dislike lisp. To me its like writing SPAs without js
Why use Windows (or MacOS, or Linux) if you don't like C?
Which aren't unreasonable questions; there are a lot of people who use XMonad despite not caring about Haskell, just because they enjoy using it.
Emacs has a much more focused UI than vscode. It's not obvious to me how to make all the extraneous things I'm not editing disappear.
The emacs-compatible extensions as far as I've seen still haven't been able to make switching files in vscode as fast and convenient as switching in emacs. I spend more time maintaining software than writing new code in a single file, so this is a noticeable slowdown.
VSCode doesn't feel as fast. I never fully investigated all the reasons. But I might make another attempt to move to it after it has a few more years to improve.
If you want to use JS, there are plenty of places to do it. Some of us just want to avoid that dumpster fire.
And if JS is so wonderful, why not make a JS editor from the ground up?
As much as I dislike elpa package manager, the mere thought of having to use npm or similar in Emacs makes me nervous already.
Is that really true?
https://github.com/search?q=repo%3Amagit%2Fmagit%20defmacro&...
I think it's fair to say that if you don't like ELisp, Emacs might be the wrong choice for you. I'm not being elitist, I just think the two are glued together even closer than POSIX and C, and it would be extremely difficult to avoid it.
Ecosystem yes, and also it's architecture and culture. ELisp I would say no. If we ignore the specific flavor, then 99% of what's realistically done with with elisp, is also covered by other dynamic languages like JavaScript. And the rest is so esoteric that it's probably not that worth the trouble.
> I don't see how supplementing ELisp with JS would make Emacs more attractive;
Not everyone likes lisp, not everyone is willing to learn a new strange language for unknown benefits. And JS has a vast ecosystem of its own. Far bigger even that Emacs heritage, but on different areas. A well working combination of both, with no side making significant sacrifices, could be very alluring for many more people than Emacs has now.