Re:Emacs-ng: A project to integrate Deno and WebRender into ...
by samus on Friday November 17, 2023 @12:58PM
(#38307297)
> You can't patch the C-core, can you? Another necessary implementation-detail.
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.
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.