all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daniele Nicolodi <daniele@grinta.net>
To: emacs-devel@gnu.org
Subject: Re: Lightweight, C-only implementation of Emacs
Date: Mon, 3 Aug 2020 16:31:11 -0600	[thread overview]
Message-ID: <6b76f688-0cd7-fd17-e980-b5945b42a21b@grinta.net> (raw)
In-Reply-To: <87tuxj4ct5.fsf@gnu.org>

On 03/08/2020 15:52, Amin Bandali wrote:
> Jeffrey Walton <noloader@gmail.com> writes:
> 
>> On Mon, Aug 3, 2020 at 3:56 PM Ulrich Mueller <ulm@gentoo.org> wrote:
>>>
>>>>>>>> On Mon, 03 Aug 2020, Jeffrey Walton wrote:
>>>
>>>>> Well, it is feature complete then.
>>>>>
>>>>> The same is true for most of the lightweight implementations in the
>>>>> list. Why would that be a problem?
>>>
>>>> "I do not recommend it use."
>>>
>>> *shrug* It compiles and works, and upstream appears to be responsive.
>>> No good reason for dropping it from a distro (and breaking existing
>>> users' workflows).
>>
>> *shrug* The author told you not to use it. What don't you understand
>> about the statement?
> 
> That's not how free software works.  The author is of course free to
> make recommendations about their software, and the community is free to
> decide to whether take the author up on that recommendation or not.

"I do not recommend its use" from an author abut the free software they
wrote has many possible meanings. Among those: "use it but please don't
bother me if it breaks and eats your data", "I know it has (serious)
flaws that I don't want even think about", "I am very tired of
supporting this piece of software, but I continue doing so for spirit of
service toward those (hopefully few) that still depend on it. Please
stop using it so I can enjoy doing something else".

Of course no one can forbid you to use the software the author himself
deprecated, but I think it would be nice to the author to follow their
recommendation and look for alternatives, or pick up or share the burden
of maintaining it.

I don't know if any of this applies to Zile, but maybe inquiring,
preferably in private, with the author and maintainer would be a good
idea before putting it in a list of suggested software (I admit I
haven't looked at the list debated here, thus I don't know if this applies).

Cheers,
Dan



  reply	other threads:[~2020-08-03 22:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-18  1:26 Lightweight, C-only implementation of Emacs Jeffrey Walton
2019-08-18  3:16 ` Bob Newell
2019-08-18  3:21 ` Noam Postavsky
2019-08-18  7:48 ` Stefan Monnier
2019-08-19  5:36 ` Ulrich Mueller
2020-08-03 18:38   ` Jeffrey Walton
2020-08-03 19:37     ` Ulrich Mueller
2020-08-03 19:42       ` Jeffrey Walton
2020-08-03 19:56         ` Ulrich Mueller
2020-08-03 19:58           ` Jeffrey Walton
2020-08-03 21:32             ` Stefan Monnier
2020-08-03 21:55               ` Gregory Heytings via Emacs development discussions.
2020-08-03 21:52             ` Amin Bandali
2020-08-03 22:31               ` Daniele Nicolodi [this message]
2020-08-03 23:56                 ` Amin Bandali
2020-08-04  1:24                   ` Daniele Nicolodi
2020-08-03 21:32           ` andres.ramirez
2020-08-07  8:38             ` Ergus
2019-08-21 22:58 ` chad
2019-09-21 15:01   ` Ergus via Emacs development discussions.

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=6b76f688-0cd7-fd17-e980-b5945b42a21b@grinta.net \
    --to=daniele@grinta.net \
    --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.