unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: 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 10:59:23 -0500	[thread overview]
Message-ID: <875yrwo3hg.fsf@dick> (raw)
In-Reply-To: <83ilvwsdxg.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Dec 2021 17:00:11 +0200")

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.



  parent reply	other threads:[~2021-12-10 15:59 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 [this message]
2021-12-10 16:44   ` Alan Mackenzie
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

  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=875yrwo3hg.fsf@dick \
    --to=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 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).