all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: eliz@gnu.org
Cc: brickviking@gmail.com, emacs-devel@gnu.org, philipk@posteo.net,
	rms@gnu.org
Subject: Re: ELPA submission: plz-see
Date: Fri, 3 Nov 2023 09:46:01 -0500	[thread overview]
Message-ID: <03d1a48e-9a2a-406b-bcce-330cab7e3402@alphapapa.net> (raw)
In-Reply-To: <83h6m36z1v.fsf@gnu.org>

>> From: Philip Kaludercic <philipk@posteo.net>
>> Cc: rms@gnu.org,  emacs-devel@gnu.org
>> Date: Fri, 03 Nov 2023 07:50:45 +0000
>> 
>> brickviking <brickviking@gmail.com> writes:
>> 
>> > I have it listed here in my elpa packages listing. A very short summary
>> > from
>> > the package itself is as follows:
>> >
>> > `plz' is an HTTP library for Emacs.  It uses `curl' as a backend, which
>> > avoids some of the issues with using Emacs's built-in `url' library.
>> 
>> And yes, the name is not indicative of what the packages does, but the
>> author had a strong preference of using a "fun" name and has advocated
>> this on multiple occasions, so it is extremely unlikely that it will
>> ever change
> 
> Too bad, FIWIW.  The name is not helpful, and I personally don't even
> find it "funny" in any sense of the word.
> 
> By proliferating packages with unhelpful names, we make ELPA and Emacs
> in general harder to use.

Please (ha) don't misunderstand me: I don't advocate for "fun" or 
"funny" names to be used exclusively for their own sake, nor at the 
expense of usefulness.  There are a number of criteria used in choosing 
a library's name, and it is ultimately a judgment call.

In the case of plz.el, all the obvious names for Elisp HTTP libraries 
were already taken (url, http, request, web).  I spent a good deal of 
time thinking about and choosing the name.  Then, when I submitted the 
package to ELPA (after having developed it for a few years), the 
alternatives suggested were long and awkward.  Then ensued a long 
discussion about how a name should be chosen, names vs. descriptions, 
concise names vs. long ones, memorable ones vs. descriptive ones, etc.

Were one of the obvious names available, I would have used it at the 
time; since none were, I chose what was the best in my judgment.  Those 
who weight criteria differently may arrive at different conclusions. 
And, yes, "fun" is one of the criteria, as is memorability.

In the end, once one finds and begins to use a tool, one tends to 
remember its name.  I would not search for "emacs" to find a text 
editor--but having found it and used it, I know what it is.

--Adam



  reply	other threads:[~2023-11-03 14:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  7:17 ELPA submission: plz-see Augusto Stoffel
2023-10-30 11:56 ` Eli Zaretskii
2023-10-31  8:09   ` Augusto Stoffel
2023-10-31  8:43   ` Philip Kaludercic
2023-10-31 20:17     ` Augusto Stoffel
2023-11-01  9:14       ` Philip Kaludercic
2023-11-01 18:36         ` Augusto Stoffel
2023-11-01 20:21           ` brickviking
2023-11-03  2:31             ` Richard Stallman
2023-11-03  6:32               ` brickviking
2023-11-03  7:50                 ` Philip Kaludercic
2023-11-03  8:06                   ` Eli Zaretskii
2023-11-03 14:46                     ` Adam Porter [this message]
2023-11-04  1:10                       ` Stefan Kangas
2023-11-04  2:10                     ` Richard Stallman
2023-11-04  5:08                       ` Adam Porter
2023-11-04  6:49                         ` Eli Zaretskii
2023-11-04  8:51                           ` tomas
2023-11-04  9:07                             ` Eli Zaretskii
2023-11-04  9:34                               ` tomas
2023-11-04 13:30                               ` Adam Porter
2023-11-04 13:56                                 ` Eli Zaretskii
2023-11-04 14:38                                   ` Adam Porter
     [not found]                               ` <877cmx4wgd.fsf@dick>
2023-11-04 13:37                                 ` tomas
     [not found]                                   ` <8734xlmwsm.fsf@dick>
2023-11-04 14:24                                     ` tomas
2023-11-04 10:38                             ` Stefan Kangas
2023-11-04 12:28                               ` Visuwesh
2023-11-04 13:17                                 ` tomas
2023-11-04 13:13                               ` tomas
2023-11-04  6:47                       ` Eli Zaretskii
2023-10-30 22:33 ` Stefan Kangas
2023-10-31  8:09   ` Augusto Stoffel
2023-11-01  0:37     ` Stefan Kangas
2023-11-01  7:29       ` Augusto Stoffel
2023-11-01 20:23         ` Stefan Kangas
2023-10-31  9:33 ` Mauro Aranda
2023-10-31 20:19   ` Augusto Stoffel

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=03d1a48e-9a2a-406b-bcce-330cab7e3402@alphapapa.net \
    --to=adam@alphapapa.net \
    --cc=brickviking@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=rms@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.