From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: emacs rendering comparisson between emacs23 and emacs26.3 Date: Tue, 31 Mar 2020 22:07:38 -0400 Message-ID: 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> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="116212"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acm@muc.de, rrandresf@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Apr 01 04:08:33 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 1jJSnw-000U94-GN for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Apr 2020 04:08:32 +0200 Original-Received: from localhost ([::1]:46058 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJSnv-0006uH-IH for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Mar 2020 22:08:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48975) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJSnA-0005yl-QJ for emacs-devel@gnu.org; Tue, 31 Mar 2020 22:07:45 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:53736) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jJSnA-0001k6-FG; Tue, 31 Mar 2020 22:07:44 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1jJSn4-0004lQ-Pa; Tue, 31 Mar 2020 22:07:38 -0400 In-Reply-To: <834ku43c61.fsf@gnu.org> (message from Eli Zaretskii on Tue, 31 Mar 2020 16:07:50 +0300) 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:246176 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > 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. 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. -- Dr Richard Stallman Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)