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: Suppressing native compilation (short and long term) Date: Sun, 02 Oct 2022 20:26:37 +0300 Message-ID: <831qrq16ia.fsf@gnu.org> References: <87bkqxf1ij.fsf@tethera.net> <8335c9dkyf.fsf@gnu.org> <83tu4odez7.fsf@gnu.org> <871qrrpkgx.fsf@trouble.defaultvalue.org> <834jwnbi6c.fsf@gnu.org> <87mtafnun5.fsf@trouble.defaultvalue.org> <83sfk6ahty.fsf@gnu.org> <87edvqno40.fsf@trouble.defaultvalue.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21303"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, david@tethera.net, emacs-devel@gnu.org, akrl@sdf.org To: Rob Browning Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Oct 02 19:29:36 2022 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 1of2mV-0005Hy-GZ for ged-emacs-devel@m.gmane-mx.org; Sun, 02 Oct 2022 19:29:35 +0200 Original-Received: from localhost ([::1]:58776 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1of2mU-00047K-9J for ged-emacs-devel@m.gmane-mx.org; Sun, 02 Oct 2022 13:29:34 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60914) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1of2jn-0008Hz-Ee for emacs-devel@gnu.org; Sun, 02 Oct 2022 13:26:48 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:50258) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1of2jm-0005cG-MT; Sun, 02 Oct 2022 13:26:46 -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=XZzAaY0hQl2+NpaPvmNPq7HdxnReqCfr6twYRD7hRMU=; b=pvrrn7m9jhHY +/MJm55i+E7MUpSJtZ85BqULWAbf14/8eSMhVXFsQ9GPl7Im6mfBHfOdXk3wEe77CYqtjZfFpGGQR 3yrEz0tRK3q9RQSH5tAyhIF6etHh73C32R7uTCsBDGFid/TQrjF/cTh0HfvsKcCPvN7JDtBfez5tG m9qgde08+SpU6tpn4M93xr/VhNbBN0cl/xyLp/7HEkWMQmbCAbBGnWbsbDSEKGOlbVnK0cree7gUY /jRdcEY7kmWK0iXcXkfneKGCbZYDgAOBY98NJG4tENlnHeOK9Byeo3GQHMqUKkl9t41tKotPsa/it YyTKEG4DOQBM85Ye8phKEQ==; Original-Received: from [87.69.77.57] (port=4194 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1of2jl-0005FT-Sq; Sun, 02 Oct 2022 13:26:46 -0400 In-Reply-To: <87edvqno40.fsf@trouble.defaultvalue.org> (message from Rob Browning on Sun, 02 Oct 2022 12:15:27 -0500) 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" Xref: news.gmane.io gmane.emacs.devel:296655 Archived-At: > From: Rob Browning > Cc: monnier@iro.umontreal.ca, david@tethera.net, emacs-devel@gnu.org, > akrl@sdf.org > Date: Sun, 02 Oct 2022 12:15:27 -0500 > > Eli Zaretskii writes: > > > Battery consumption doesn't seem very relevant, because JIT > > compilation will happen when the system is used, not when it sleeps. > > And it is entirely not guaranteed that by compiling everything you > > will save power in the long run, because there are good chances you > > will be compiling stuff that won't be used for a long time. Without > > quantitative data of long-term power usage on which to base the > > conclusions, I don't see why you should a-priori assume that compiling > > everything from the get-go should use less power. Same goes for disk > > space by multiple users. > > On this particular topic, I was actually just communicating a concern > that was communicated to me -- that a user wasn't happy about the > unpredictable, compilation spike long after the install on their laptop, > (in part due to concerns about power consumption). That's just something that takes getting used to. > (Personally, as a user, I'd also prefer to pay the cost up front, most > of the time, during package install, and to avoid per-user duplications > where possible, but that said, I generally do try to avoid basing > Debian packaging decisions solely on my preferences, and I do want to > try to favor upstream preferences in general.) Those seem like old habit that die hard, IMO. For users of some programming languages, JIT compilation is routine, and I bet they don't share these habits.