From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacs rendering comparisson between emacs23 and emacs26.3 Date: Wed, 01 Apr 2020 16:23:59 +0300 Message-ID: <83k12zz6ds.fsf@gnu.org> References: <86tv2h2vww.fsf@gmail.com> <20200322123818.GB32470@ACM> <87eetk5swm.fsf@gnu.org> <20200326193128.GC14092@ACM> <86d08y4zsx.fsf@gmail.com> <83sghs7qdz.fsf@gnu.org> <83h7y63sjj.fsf@gnu.org> <834ku43c61.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="87189"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acm@muc.de, rrandresf@gmail.com, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Apr 01 15:24:26 2020 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 1jJdM1-000MYF-2e for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Apr 2020 15:24:25 +0200 Original-Received: from localhost ([::1]:60296 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJdM0-0000YN-42 for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Apr 2020 09:24:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37726) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJdLU-0008Hh-U5 for emacs-devel@gnu.org; Wed, 01 Apr 2020 09:23:53 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:60932) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jJdLU-0008HS-J4; Wed, 01 Apr 2020 09:23:52 -0400 Original-Received: from [176.228.60.248] (port=2085 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jJdLM-0004Y2-LA; Wed, 01 Apr 2020 09:23:45 -0400 In-Reply-To: (message from Richard Stallman on Tue, 31 Mar 2020 22:07:38 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:246188 Archived-At: > From: Richard Stallman > Cc: acm@muc.de, rrandresf@gmail.com, emacs-devel@gnu.org > Date: Tue, 31 Mar 2020 22:07:38 -0400 > > > When we know a new feature causes significant slowdown, we either fix > > it, or provide a way to disable or work around it. The problem is, we > > don't always know there's slowdown, as it frequently happens only in > > specific rare use cases. > > 1. If the slowdown cases are truly rare, I don't think they will bother > users very often. A frequent case is that the use case is rare on the average, but for some user(s) it is not so rare. > 2. I think we should be able to anticipate which changes _might_ cause > noticeable slowdowns. They will be changes that will come into play > frequently in basic activities such as cursor motion, basic editing > operations, or redisplay. We may not anticipate 100%, but let's start > trying. I think we do try: patch review frequently has these aspects discussed. But it is a well known fact that humans are lousy predictors of code speed, which is why the advice is always to profile before deciding where to optimize. I think we miss the slowdowns for the same reason.