unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: Package "luwak"
Date: Sat, 17 Dec 2022 22:21:49 -0500	[thread overview]
Message-ID: <E1p6kFJ-0006ot-ES@fencepost.gnu.org> (raw)
In-Reply-To: <E1p6Cig-0004RG-Ij@fencepost.gnu.org> (ams@gnu.org)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > The main issue that I think Richard wants to tackle is
  > discoverability.

The two goals I am concerned about are (1) discoverability and (2)
understandability.  "Luwak" is bad on both of those dimensions.  Even
if you read about the package 6 months ago, you are likely not to
recall what it does, because the name does nothing to help you recall.

                      So while luwak as a name is is meaningless, doesn't
  > mean that it in itself is a bad name -- it is unique, and easy to
  > remeber.

In my view, meaningless names are bad names.  Mere uniqueness is not
enough to make up for the lack of discoverability and
understandability.

There can be unusual cases where a unique, meaningless name might
suffice: for a feature that is so important and so often used that
everyone will encounter the feature every week, perhaps we can expect
all users to learn and remember what it does.

In those cases, perhaps it won't matter than the name is meaningless.

But such cases are unusual.

  > Instead of trying to find "perfect" names

By saying "perfect", that sentence criticizes bvy exaggeration.  I am
not calling for "perfect" names.  What I said is nothing like that.

I am calling for an effort to look for a name that is at lesst
somewhat helpful -- rather than adopting a totally unhelpful name
that has no reasons to prefer it.

    wouldn't it make more sense to have another
  > field, or extend the Keywords field?

That might be a good idea; how about posting a proposal
in a different thread with a different subject line.

But that wouldn't eliminate the benefit of a name that is meaningful
and helpful.


-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  parent reply	other threads:[~2022-12-18  3:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 23:51 Package "luwak" Richard Stallman
2022-12-01  0:52 ` Stefan Monnier
2022-12-02 22:51   ` Richard Stallman
2022-12-03  2:49     ` T.V Raman
2022-12-11  4:04       ` Yuchen Pei
2022-12-04 23:18   ` Will Mengarini
2022-12-05  4:25     ` Jean Louis
2022-12-05 22:30     ` Richard Stallman
2022-12-06  9:05       ` Philip Kaludercic
2022-12-06 22:37         ` Richard Stallman
2022-12-07  3:33           ` Eli Zaretskii
2022-12-07  7:11             ` Philip Kaludercic
2022-12-07  8:44               ` Andreas Schwab
2022-12-01  3:54 ` North Year
2022-12-11  3:54 ` Yuchen Pei
2022-12-11 23:34   ` Richard Stallman
2022-12-11 13:07 ` Yuchen Pei
2022-12-12 22:19   ` Richard Stallman
2022-12-11 14:29 ` Stefan Monnier
2022-12-11 18:03   ` Tim Cross
2022-12-12 22:19   ` Richard Stallman
2022-12-12 22:42     ` Philip Kaludercic
2022-12-13 23:58       ` Richard Stallman
2022-12-14 21:34         ` Philip Kaludercic
2022-12-14 21:41           ` [External] : " Drew Adams
2022-12-16  3:35           ` Richard Stallman
2022-12-16 15:33             ` Alfred M. Szmidt
2022-12-16 17:31               ` [External] : " Drew Adams
2022-12-16 18:52                 ` Alfred M. Szmidt
2022-12-18  3:21               ` Richard Stallman [this message]
2022-12-16 11:05           ` Jean Louis

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=E1p6kFJ-0006ot-ES@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=ams@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    /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).