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: Mon, 11 Sep 2023 15:24:43 +0300 Message-ID: <83r0n4rj78.fsf@gnu.org> References: <87ledwx7sh.fsf@yahoo.com> <877cpfybhf.fsf@yahoo.com> <873503y66i.fsf@yahoo.com> <87fs3ur9u8.fsf@dataswamp.org> <875y4moiiq.fsf@dataswamp.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5056"; mail-complaints-to="usenet@ciao.gmane.io" Cc: incal@dataswamp.org, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Sep 11 14:26:14 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 1qffza-0001dy-RC for ged-emacs-devel@m.gmane-mx.org; Mon, 11 Sep 2023 14:26:14 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qffyr-00063U-KU; Mon, 11 Sep 2023 08:25:29 -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 1qffyo-00063I-TW for emacs-devel@gnu.org; Mon, 11 Sep 2023 08:25:27 -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 1qffyn-0001al-UG; Mon, 11 Sep 2023 08:25:25 -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=lrY3roRQF8rZkHFbzwy/uhLe7Rrxzv9DOys6IqVqdtA=; b=fFnNzECSa1dk 5Lyg8Qzb0H1QIjHwk6UBq5LJoWiVT7ruF5BHwHdDue0E+6MRpx32R8+qHU8UwmNTPPFsS0TehgWnC +i5zPV/uCxqVgXWjPISDL0bXQIjXYeTTO74pLQaqY62bS+WKqR3fIbGAYgnH6Cgj0Vq6a3V6ZCMKW e+I1L3E0Ko8KFBCo4EmMrh934morN3cmnxZRMbrqWV5xZXXO8UxeIDhVG22UoCtgLixBNzGSAVH2o QmzxdJWJUC44q7xGGPEH9cJqOiH/LOOTdicZxCYzfIjqS4wx3snSFYjpaJMPb/RsnMJMSI7DZc97o bhW+D2ZABqzGKfjOwAaniw==; In-Reply-To: (message from Richard Stallman on Sun, 10 Sep 2023 20:43:01 -0400) 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:310480 > From: Richard Stallman > Cc: emacs-devel@gnu.org > Date: Sun, 10 Sep 2023 20:43:01 -0400 > > > You are right, absolutely, but then I cannot see why people > > can't push for a SBCL rewrite of Emacs? > > Because that is not up for decision. That decision is already made. > > If the question were up for decision, arguing for a certain choice > would be normal participation. When it isn't, arguing for a choice is > making life difficult. I have too much work to do, and I can't keep > up. So does Eli. Eli can speak for himself, but if you make it necessary > for me to spend more time on this, that is making difficulties. IMNSHO, discussing a rewrite of Emacs in _any_ language is waste of time and energy. We've seen this many times (because people still insist on bringing this up from time to time). From where I stand, the main reason is not even the fact that we decided not to do that, but the fact that such a rewrite will never happen in practice. Such a rewrite is a massive job which requires very good knowledge of Emacs internals and features, and a lot of time. People who come close to the required knowledge level are not interested in doing this job (because they understand the futility), and those who think it should be done simply don't know enough and/or don't have enough time on their hands to pull it through. If Emacs will ever be "rewritten", it will not be Emacs, but a text-processing system with a very different architecture and design, which will take from the Emacs experience the lessons we learned and implement them differently, to produce a system whose starting point is closer to the needs of today's users and whose main technologies are more modern from the get-go.