logoalt Hacker News

conartist6today at 4:49 PM6 repliesview on HN

I chose the JS ecosystem. Why does the power of Emacs not belong in the browser? These days JS is a powerful enough FP language to do it.


Replies

throwaway27448today at 10:13 PM

No, the power of the browser belongs in emacs. You're composing the wrong direction!

Anyway aren't you just describing vscode?

show 1 reply
BeetleBtoday at 8:58 PM

Because to replicate the power of Emacs, you'd need to throw away a lot of privacy/security in the browser. You'd need to let one tab read the contents of another by default. A change to make your mail reading better may break your banking app (yes, that's a reality with Emacs).

Also, Emacs windows vs tabs. Think of having each tab be a non-overlapping window within the browser window.

Finally, most browsers don't let JS code modify the browser itself. If I suddenly decide I'd like Firefox's menu completely rearranged, I don't think JS will give it to me.

show 1 reply
iLemmingtoday at 8:45 PM

Because you need Lisp. That's the actual "power of Emacs". Emacs is a Lisp-interpreter with a built-in text editor. Everything stems from that. Anyone challenging "the choice" of Lisp as the configuration language for an editor, saying things like: "Why? If X is better - faster, more modern, more popular...", etc., have misunderstanding of what makes Lisp so uniquely powerful.

A specific language is not the point - to implement anything similar to Emacs, you'd need a homoiconic language or at least a language that gives you live, reflective, late-bound image with code-as-data. Without that single aspect tons of things simply and inevitably (as history shows) will get complicated.

Why we have not seen such differentiator with VSCode? Because of their design choices - the extension language and the editor internals live in different worlds behind an API boundary. Emacs essentially has no such boundary. That's the power, and also a consequence of the image + homoiconicity combo.

show 1 reply
getpokedagaintoday at 7:37 PM

Nearly 40 years of stuff.

People iterating on a problem space over time is the best way we have found to improve things.

The JS ecosystem is not that old and also attempts to solve hundreds of unrelated problems like running software without peoples consent.

show 2 replies
all2today at 5:21 PM

They told me the future would have horrors beyond my comprehension.

But I understand this particular horror. I might even agree... :D

m463today at 7:06 PM

Maybe python can't do it, but I would love to extend my editor (and even browser) using python.

show 1 reply