unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: JD Smith <jdtsmith@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Moving packages out of core to ELPA
Date: Sun, 18 Feb 2024 07:57:00 -0500	[thread overview]
Message-ID: <E87AD60F-C96B-4F04-8CE7-283C8C8C4A8E@gmail.com> (raw)
In-Reply-To: <86r0has2v3.fsf@gnu.org>



> On Feb 18, 2024, at 1:28 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: JD Smith <jdtsmith@gmail.com>
>> Date: Sat, 17 Feb 2024 16:16:31 -0500
>> Cc: emacs-devel@gnu.org
>> 
>>>> Not necessarily, depending on how one defines obsolete. Just “no longer worth keeping in core”.
>>> 
>>> That's not my interpretation of your description of IDL state.
>> 
>> Then I fear you may have misinterpreted me.  Many astronomers and earth scientists do still use it. A few with emacs.  Maybe it’s a bit like Perl that way.  There’s a lot of legacy code around. So it’s perfectly valuable to keep in ELPA, but IMO the cost/benefit no longer merits inclusion in core.
> 
> Why doesn't the cost/benefit merit inclusion in core?

Maybe I should be more specific here: I don't think the cost/benefit favors having it in the core ready to fire up when any .pro file is loaded (since there are other unrelated flavors with that file type in the wild, e.g. Qt config files, which confuses people), or having the IDLWAVE manual appear at the top level of M-x info (as nice as a manual it is, and as hard as I worked on it lo those many years ago).

> How do you understand the considerations for keeping something in core
> in general?

When the additional burden of extra information presented to users and the costs to maintain, update, seek out and correct outdated code is outweighed by the utility some users gain by having it readily at hand.  A small package that is effectively invisible and never loads unless the user summons it has fewer costs in this way of looking at it.  I do not suggest that judging this balance is trivial or even straightforward, but it's my opinion for this particular package, many of whose users I am well familiar with, the costs outweigh the benefits.  I am interested in how the maintainers proper see the costs of maintenance; maybe I overestimate those.  And I do note there are lots of things under M-x info that probably don't see much use, so I acknowledge these arguments could represent a "slippery slope".


  reply	other threads:[~2024-02-18 12:57 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-17 14:40 Moving packages out of core to ELPA JD Smith
2024-02-17 15:51 ` Eli Zaretskii
2024-02-17 16:22   ` JD Smith
2024-02-17 16:51     ` Eli Zaretskii
2024-02-17 17:08       ` JD Smith
2024-02-17 17:29         ` Eli Zaretskii
2024-02-17 18:52           ` JD Smith
2024-02-17 19:20             ` Eli Zaretskii
2024-02-17 20:56               ` [External] : " Drew Adams
2024-02-17 21:16               ` JD Smith
2024-02-18  6:28                 ` Eli Zaretskii
2024-02-18 12:57                   ` JD Smith [this message]
2024-02-18 13:46                     ` Po Lu
2024-02-18 14:03                       ` JD Smith
2024-02-18 14:08                         ` Po Lu
2024-02-18 14:17                           ` JD Smith
2024-02-18 14:17                         ` Eli Zaretskii
2024-02-18 14:19                           ` JD Smith
2024-02-18 14:22                         ` Po Lu
2024-02-17 17:42         ` [External] : " Drew Adams
2024-02-17 18:21           ` JD Smith
2024-02-17 18:32             ` Eli Zaretskii
2024-02-17 19:01               ` JD Smith
2024-02-17 20:50               ` Drew Adams
2024-02-18  1:55         ` Po Lu
2024-02-18  2:27           ` JD Smith
2024-02-18  3:47             ` Po Lu
2024-02-18  1:42 ` Po Lu
2024-02-18  2:14   ` JD Smith
2024-02-18  3:39     ` Po Lu
2024-02-18  7:25       ` Po Lu
2024-02-18 12:39       ` JD Smith
2024-02-18 13:08         ` Eli Zaretskii
2024-02-18 13:15         ` Po Lu
2024-02-18  7:14     ` Eli Zaretskii
2024-02-18 12:19       ` Dmitry Gutov
2024-02-18 13:06         ` Eli Zaretskii
2024-02-18 13:27           ` JD Smith
2024-02-18 13:06         ` Po Lu
2024-02-18 13:13           ` Dmitry Gutov
2024-02-18 13:51             ` Po Lu
2024-02-18 14:19               ` Dmitry Gutov
2024-02-18 14:26                 ` Po Lu
2024-02-18 14:38                   ` Dmitry Gutov
2024-02-19 18:09           ` Stefan Kangas

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=E87AD60F-C96B-4F04-8CE7-283C8C8C4A8E@gmail.com \
    --to=jdtsmith@gmail.com \
    --cc=eliz@gnu.org \
    --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).