From: Alan Mackenzie <acm@muc.de>
To: dick <dick.r.chiang@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master c9cb59b 2/2: * etc/TODO: Entry about converting to defvar-keymap.
Date: Fri, 10 Dec 2021 16:44:09 +0000 [thread overview]
Message-ID: <YbOD2RI0XcnyjkUl@ACM> (raw)
In-Reply-To: <875yrwo3hg.fsf@dick>
Hello, Dick.
On Fri, Dec 10, 2021 at 10:59:23 -0500, dick wrote:
> EZ> I see only a lot of code churn and a risk of breaking things that
> EZ> are perfectly fine as they are.
> To most gatekeepers, spaghetti code is "perfectly fine" if no one
> complains. And so long as the spaghetti is of their own making, let
> newcomers to the code spin their tires trying to modify it.
> Incomprehensibility is an excellent, natural defense.
> Churn should never be a deterrent; cleanliness is next to godliness.
> Any programmer with his salt can see that.
Really, must you keep on doing this?
It seems the only purpose of your post here was to aggravate Eli. Any
policy direction can be countered by a trite meaningless phrase like
"cleanliness is next to godliness"; it seems likely, had Eli expressed
the opposite direction, you would have chastised him for encouraging the
wasting of time, in an equally trite and unpleasant manner.
Please stop posting like this. It doesn't help anybody.
If you want to contribute positively to Emacs, in whatever manner, I'm
sure you'd be welcome. But you know how the project works, what it's
doing, and likely why; you're not going to be able to change these
things. It you don't like them, why stick around?
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2021-12-10 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 15:00 master c9cb59b 2/2: * etc/TODO: Entry about converting to defvar-keymap Eli Zaretskii
2021-12-10 15:37 ` Stefan Kangas
2021-12-10 16:51 ` Eli Zaretskii
2021-12-11 3:02 ` Lars Ingebrigtsen
2021-12-11 6:20 ` Stefan Kangas
2021-12-10 15:59 ` dick
2021-12-10 16:44 ` Alan Mackenzie [this message]
2021-12-11 0:56 ` Po Lu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YbOD2RI0XcnyjkUl@ACM \
--to=acm@muc.de \
--cc=dick.r.chiang@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.