From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.devel Subject: Re: What's missing in ELisp that makes people want to use cl-lib? Date: Sat, 11 Nov 2023 14:10:20 +0100 Message-ID: <87edgwigg3.fsf@dataswamp.org> References: <871qd8sfdx.fsf@posteo.net> <838r7g8pys.fsf@gnu.org> <87bkcbrgnr.fsf@posteo.net> <25924.21015.19614.951576@orion.rgrjr.com> <87bkc4jpja.fsf@dataswamp.org> <12da6bcb-1818-7fbe-12af-8d4607724332@gutov.dev> <83sf5fyx60.fsf@gnu.org> <83o7g3ynjp.fsf@gnu.org> <87h6lvhrme.fsf@dataswamp.org> <83jzqrylte.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31402"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:rd+0H9o+hQNVtcfKrApnyFBpP/Y= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Nov 11 14:39:20 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1r1oCm-0007yK-7y for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Nov 2023 14:39:20 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r1oCY-00083j-4b; Sat, 11 Nov 2023 08:39:06 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r1nky-0000yr-6v for emacs-devel@gnu.org; Sat, 11 Nov 2023 08:10:36 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r1nkt-0007zZ-HJ for emacs-devel@gnu.org; Sat, 11 Nov 2023 08:10:35 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1r1nkp-0003P4-K5 for emacs-devel@gnu.org; Sat, 11 Nov 2023 14:10:27 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Sat, 11 Nov 2023 08:39:05 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:312558 Archived-At: Eli Zaretskii wrote: > This is a volunteer-based project, so we have no way of > "distributing the maintenance effort", unless people > volunteer to do it. In particular, for absolute majority of > the Emacs code, the people who wrote the code are no longer > on board. That's the reality. > > If you mean that the authors who are still here should be > asked to take care of their code, then this is already being > done, always, and cannot be done to any higher degree. Yes, I understand, but we can still just hand out files to people, "now you are maintaining this file". That person will have to agree, of course. For each such file handed out there is one file less for the "maintainers of everything else" to handle. Because what we heard was that there are often just a few uses of cl-lib in some person's code, and that is manageable to learn for the maintainer. Only in some other person's code, there are also just a few such cases, but not necessarily the same, so the maintainers of a lot of files, for them the complexity increases for each file even tho the individual files are not complex in their us of, say, cl-lib, really. So if we give away a bunch of files to a larger group of people, those people will not have an issue with cl-lib, really, and at the same time both scope and complexity will be reduced for the "everything else" maintainers. -- underground experts united https://dataswamp.org/~incal