From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Lift {global,local}-key-binding to Lisp
Date: Fri, 15 Jan 2021 05:16:20 +0100 [thread overview]
Message-ID: <87o8hqhm23.fsf@telefonica.net> (raw)
In-Reply-To: 83lfcvb7pj.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> Emacs will be around in 40-50 years still, and we should maintain it
>> with that in mind. Every time we make code more readable and
>> maintainable, we make our life easier in the long run.
>
> I don't really see how moving stuff to Lisp in these cases makes the
> code more readable or maintainable. You basically wrote the same code
> in Lisp as it was in C.
>
>> Of course, any such change taken in isolation will look like something
>> we could also live without, but many such incremental improvements over
>> time will start to make a difference for the better. Clean and
>> maintainable code is a good thing, and Lisp is better for that than C.
>
> I disagree, so let's please not do that unless we also add some
> significant improvements or simplification.
Along the years you repeatedly and justly expressed concerns about the
future maintenance of the C code base due to lack of hackers with the
required skills. Anything that reduces the number of lines of C will
mitigate that concern. Plus, moving things to Elisp will remove the
requirement of knowing C (and all its Emacs-specifc idioms) for hacking
on the corresponding features.
I look forward to the time when, thanks to native-comp and FFI,
everything is implemented on Elisp except for a tiny C core. Looking at
the Emacs C source code it is clear that it was written with an
"i-would-rather-be-doing-this-on-Lisp" mindset. Let's go for the real
thing.
next prev parent reply other threads:[~2021-01-15 4:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 19:26 Lift {global,local}-key-binding to Lisp Eli Zaretskii
2021-01-14 19:24 ` Stefan Kangas
2021-01-14 20:10 ` Eli Zaretskii
2021-01-14 20:24 ` Eli Zaretskii
2021-01-15 1:58 ` Leo Liu
2021-01-15 4:16 ` Óscar Fuentes [this message]
2021-01-15 7:42 ` Eli Zaretskii
2021-01-21 16:03 ` Stefan Kangas
2021-01-21 16:59 ` [External] : " Drew Adams
2021-01-21 17:50 ` Dmitry Gutov
2021-01-21 18:16 ` Drew Adams
2021-01-21 18:58 ` Dmitry Gutov
2021-01-21 19:59 ` Eli Zaretskii
2021-01-14 21:03 ` Andrea Corallo via Emacs development discussions.
2021-01-15 7:45 ` Eli Zaretskii
2021-01-15 12:09 ` Dmitry Gutov
2021-01-15 12:18 ` Eli Zaretskii
2021-01-15 13:24 ` Dmitry Gutov
2021-01-15 13:45 ` Eli Zaretskii
2021-01-15 18:09 ` Dmitry Gutov
2021-01-17 14:27 ` Christopher Miles
2021-01-15 18:03 ` Drew Adams
2021-01-16 0:51 ` Leo Liu
2021-01-17 14:33 ` Christopher Miles
2021-01-17 15:08 ` Eli Zaretskii
2021-01-18 3:29 ` Christopher Miles
2021-01-18 16:43 ` Eli Zaretskii
2021-01-17 16:10 ` Basil L. Contovounesios
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8hqhm23.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).