From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Is Elisp really that slow? Date: Sun, 12 May 2019 21:53:41 +0300 Message-ID: <83ftpjbj2i.fsf@gnu.org> References: <20190502214006.4fdsinp7u5xuqvdv@Ergus> <20190503004416.xfuzzucflp6bxpuz@Ergus> <8736lm30lz.fsf@web.de> <864l61j04d.fsf@zoho.eu> <20190511073254.GB29829@tuxteam.de> <04187AB9-AD7D-492D-A890-BCB01848370C@icloud.com> <20190511075712.GD29829@tuxteam.de> <86a7fsfv1m.fsf@zoho.eu> <20190512075448.GA11650@tuxteam.de> <346107E9-590D-4A18-9152-ECFF36FC4EDC@icloud.com> <83r293bvok.fsf@gnu.org> <87ef53vihw.fsf@telefonica.net> <83mujrbsk7.fsf@gnu.org> <87a7frvfo1.fsf@telefonica.net> <83h89zbndc.fsf@gnu.org> <875zqfv7sb.fsf@telefonica.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="68846"; mail-complaints-to="usenet@blaine.gmane.org" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun May 12 20:54:16 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hPtbz-000HoQ-Tj for geh-help-gnu-emacs@m.gmane.org; Sun, 12 May 2019 20:54:16 +0200 Original-Received: from localhost ([127.0.0.1]:46243 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPtby-0004If-Oa for geh-help-gnu-emacs@m.gmane.org; Sun, 12 May 2019 14:54:14 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:35971) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPtbl-0004Ia-Em for help-gnu-emacs@gnu.org; Sun, 12 May 2019 14:54:02 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:60395) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPtbl-00078K-Bd for help-gnu-emacs@gnu.org; Sun, 12 May 2019 14:54:01 -0400 Original-Received: from [176.228.60.248] (port=2455 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hPtbj-0005PV-P2 for help-gnu-emacs@gnu.org; Sun, 12 May 2019 14:54:00 -0400 In-reply-to: <875zqfv7sb.fsf@telefonica.net> (message from =?utf-8?Q?=C3=93scar?= Fuentes on Sun, 12 May 2019 20:37:08 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:120326 Archived-At: > From: Óscar Fuentes > Date: Sun, 12 May 2019 20:37:08 +0200 > > When I started with Emacs around 20 years ago, whenever something was > incorrectly indented or fontified on C++ code I was writing it indicated > an error on my part. It was way ahead of any other editor. Nowadays CC > Mode can't handle C++ code styles and constructs that became available > shortly afterwards the period I mentioned. For languages that became > popular since the 1990's Emacs is barely adequate on some cases and a > non-starter on others. > > I'm certainly frustrated because this is a self-inflicted problem. > Emacs' high-governance (and I mean "really high", you know what I mean) > forced some very bad decisions upon the project (and not only on Emacs) > which put us all, developers and users, on a really difficult position. If you want to explain the problems of CC Mode by some "governance", you are dead wrong, AFAIK. The real reasons, IMO, are entirely different. At the very least, it was never proven that this has anything to do with the problems we have. Anyone who tracks emacs-devel could easily formulate an alternative hypothesis, which IMO is much more probable. In general, problems in Emacs are rarely if ever due to management (which doesn't really exist), they are almost always due to lack of manpower, expertise, talent, free time, motivation, etc. > I have on my to-do list for this year to grab Tromey's JIT branch and > migrate it to LLVM and see what the optimization passes can squeeze, > possibly with some simple static analysis and, if I'm in the mood, type > annotations on Elisp code. The JIT branch doesn't really work, and I have yet to see any speedup from it in the configurations where it does compile. So from my POV, that experiment is a failure, and (having spent more than one or two hours on making it work better) I see no reason why the failure could be fixed by using LLVM, because libjit doesn't use any compiler in the first place. So, here too, I see a very weak connection, to say the least, between your suspected reasons and the reality as I know it.