From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Shrinking the C core Date: Fri, 11 Aug 2023 16:16:43 +0300 Message-ID: <83350phg78.fsf@gnu.org> References: <20230809094655.793FC18A4654@snark.thyrsus.com> <87il9owg0f.fsf@yahoo.com> <87ttt7odzh.fsf@arch.mail-host-address-is-not-set> <87leej7ima.fsf@gentoo.org> <83y1iigmh4.fsf@gnu.org> <87edkat1a4.fsf@dataswamp.org> <83a5uxhlel.fsf@gnu.org> <87edk9kcbn.fsf@dataswamp.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8785"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Emanuel Berg Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Aug 11 15:17:03 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 1qUS0l-00026Y-0r for ged-emacs-devel@m.gmane-mx.org; Fri, 11 Aug 2023 15:17:03 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qUS03-0007yI-Cb; Fri, 11 Aug 2023 09:16:19 -0400 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 1qUS00-0007xM-VJ for emacs-devel@gnu.org; Fri, 11 Aug 2023 09:16:17 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qURzy-00048M-EH; Fri, 11 Aug 2023 09:16:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=6HeEPuMsNOb31R3eo4Mufq68/uWEUdC4m80jGdX9wq8=; b=Kkw/ocKlNMZl BUSCkC4XRdFPVbUsr7+XBPIxsX60Ldm2+A3IrDhTxSQR2nsz3LYU1GDnG8k6d03dk8Z3JJ5KP1HMT fRmVtakh/7CdWrSR8d9VaNhOK2+N9Edh65QH9HfKVDp+3KiZQDwF1CvWyPNV0r8v9OeuN75X/APyr +7bAand17IxT76r788sVyerBE2BThkxDa4thYHkNT4g1IyTHl8nzY6x9RbZ2Uw8yrRwvtTxA3Y1+o sgDum0t6ToykjVyLge69lq1+eSUZRSE9fjnIcb/bzV8HVXdl8xFD2a9XZWhISwUVXWQ6mIWHssvVF Ota2UjAhy+gdzyfvlE1W/g==; In-Reply-To: <87edk9kcbn.fsf@dataswamp.org> (message from Emanuel Berg on Fri, 11 Aug 2023 14:12:12 +0200) 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:308580 Archived-At: > From: Emanuel Berg > Date: Fri, 11 Aug 2023 14:12:12 +0200 > > Eli Zaretskii wrote: > > >>> Moving old and well-tested C code out to Lisp usually > >>> _increases_ maintenance burden, because the old code in > >>> most cases needs _zero_ maintenance nowadays. > >> > >> One could maybe identify certain slow spots in Elisp and > >> see if there would be a point moving them to C. > > > > Yes, and we are doing that. > > Okay, what spots are those, and how do you find them? We usually find them by profiling, or by finding we need functionalities that would be hard or impossible to implement in Lisp.