From: Samuel Wales <samologist@gmail.com>
To: emacs-tangents@gnu.org
Subject: Re: emacs-devel/debbugs communication (was: New Package for NonGNU-ELPA: clojure-ts-mode)
Date: Mon, 4 Sep 2023 21:06:19 -0700 [thread overview]
Message-ID: <CAJcAo8sHL45sx+TUn+rV8SWi4wzvJeexUn7asoDGDw-sSvAGyA@mail.gmail.com> (raw)
In-Reply-To: <8734ztpgru.fsf@dataswamp.org>
i thought nobody serious about emacs suggests rewriting existing elisp
but rather rebasing it?
On 9/4/23, Emanuel Berg <incal@dataswamp.org> wrote:
> Richard Stallman wrote:
>
>>> 1. Maintainers often say "no" to certain things (like code
>>> refactoring that does not lead to any clear improvement)
>>> because they know from their extensive experience that
>>> some ideas are "non-starters". However, they do not
>>> elaborate much why one or another thing is
>>> not acceptable.
>>>
>>> Not elaborating is actually perfectly understandable -
>>> it would be annoying to repeat the same thing many times
>>> and would also waste the maintainer's valuable time that
>>> could be spent for something more productive.
>>
>> I think I can understand why this feels painful -- but what
>> concretely could we ask the maintainers to do which would be
>> better overall?
>
> gnu.emacs.devel FAQ!
>
> I. BAD IDEAS AND WHY THEY ARE BAD
>
> 1. Idea: Drop Elisp, instead use SBCL for Emacs
>
> Argument:
>
> SBCL is faster and has parallelism for modern multicores.
> We would be able to use everything the SBCL community has
> developed. For the supposed Lisp editor, we would have the
> most relentless and cruel Lisp on Earth, instead of the
> half-goofy Elisp which some people think is just used to set
> a bunch of options.
>
> Why it is STILL a bad idea:
>
> Elisp is now also very fast with native-compilation and it
> is likely it will get even faster as that technology is
> quite new, and is being actively developed. Elisp is also
> much more portable than SBCL. The SBCL speed advantage and
> parallelism relies on specific constructs the programmer has
> to add explicitly in the code. So all our Joe Hacker's Elisp
> wouldn't benefit from that in its current state. Not to
> mention all our Joe Hacker's Elisp would have to be
> re-written and adopted into SBCL. To re-write Emacs so that
> its Lisp would be SBCL and not Elisp would be an insanely
> big undertaking with a very unclear image what the result
> would be. Remember, one shouldn't burn down the house to
> kill the rats. Also, there are Emacs-like editors already
> that are based on CL. So we are not doing it, goddammit!
>
> --
> underground experts united
> https://dataswamp.org/~incal
>
>
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
next prev parent reply other threads:[~2023-09-05 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87il9kksqz.fsf@dfreeman.email>
[not found] ` <83350ncbns.fsf@gnu.org>
[not found] ` <87cyzrjbd8.fsf@dfreeman.email>
[not found] ` <83zg2vav46.fsf@gnu.org>
[not found] ` <87o7j99304.fsf@dfreeman.email>
[not found] ` <CADwFkm=XLwqh1xFxGu7Nci=Z-t3F9vzRHPxwAcoE6h_a6p-WWA@mail.gmail.com>
[not found] ` <97224c4f-fad4-ae01-46c1-5755d97d9a92@gutov.dev>
[not found] ` <CADwFkmn29hGxKpWTEKPXVWcaV9evpg2CEg0GR1j_3_GkPOsUJg@mail.gmail.com>
[not found] ` <c45dffbc-6f7f-6b47-0689-0580268d6656@gutov.dev>
[not found] ` <87fs3ztq38.fsf@localhost>
[not found] ` <87cyz3qwba.fsf@posteo.net>
[not found] ` <8734zztmiz.fsf@localhost>
[not found] ` <87sf7zqs3l.fsf@yahoo.com>
[not found] ` <87il8vs6e7.fsf@localhost>
[not found] ` <87jztbqrc9.fsf@yahoo.com>
[not found] ` <877cpbs5a0.fsf@localhost>
[not found] ` <87fs3zqqgj.fsf@yahoo.com>
[not found] ` <874jkfs4o0.fsf@localhost>
[not found] ` <87y1hroz47.fsf@posteo.net>
[not found] ` <e5418514-5a15-469f-d797-0b9668fc2879@vodafonemail.de>
[not found] ` <E1qcFnL-0008QG-3Q@fencepost.gnu.org>
[not found] ` <87wmx7mzcf.fsf@localhost>
2023-09-05 0:29 ` emacs-devel/debbugs communication (was: New Package for NonGNU-ELPA: clojure-ts-mode) Richard Stallman
2023-09-05 1:09 ` Emanuel Berg
2023-09-05 4:06 ` Samuel Wales [this message]
2023-09-05 13:57 ` Emanuel Berg
2023-09-06 10:04 ` Ihor Radchenko
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=CAJcAo8sHL45sx+TUn+rV8SWi4wzvJeexUn7asoDGDw-sSvAGyA@mail.gmail.com \
--to=samologist@gmail.com \
--cc=emacs-tangents@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.
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).