From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.devel Subject: Re: [External] : Re: Default custom file was: Re: Propose to add setup-wizard.el to ELPA Date: Tue, 11 Jan 2022 23:35:50 +1100 Message-ID: <87h7aaz9gj.fsf@gmail.com> References: <871r1k38ym.fsf@gmail.com> <87ee5kmm6t.fsf@gmail.com> <87a6g8m1n1.fsf@gmail.com> <871r1jm4hf.fsf@gmail.com> <8735lupwt1.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36364"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.7.5; emacs 28.0.91 To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 11 15:26:06 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 1n7I69-0009HF-Ve for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Jan 2022 15:26:06 +0100 Original-Received: from localhost ([::1]:41282 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n7I68-0003Xh-Il for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Jan 2022 09:26:04 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58732) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7HEC-0006ld-Jt for emacs-devel@gnu.org; Tue, 11 Jan 2022 08:30:29 -0500 Original-Received: from [2607:f8b0:4864:20::1031] (port=56048 helo=mail-pj1-x1031.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n7HEA-0002PL-As for emacs-devel@gnu.org; Tue, 11 Jan 2022 08:30:19 -0500 Original-Received: by mail-pj1-x1031.google.com with SMTP id hv15so11242435pjb.5 for ; Tue, 11 Jan 2022 05:30:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:user-agent:from:to:subject:date:in-reply-to:message-id :mime-version:content-transfer-encoding; bh=UOidZ3mfRBC2F7ySOmmj3g3IjKdY/VQ4CD9vtYW/7lc=; b=FjIWlNvhCQgv4aEwcDuLB9gjyNXbkPBKaoHsjqtwDOVbEEvDHD0FAvQBpkMXa8eCJT QHI2Ka3nNZJ5QgcP+GITRcKokomJBazW03IvUzLfNt+Q2nHlQhhs5xBLd1RAdkagPfZf LwaNTwHASH7RFmLlaHW33P/cqKhWM89INC+7zR6r+mpYaAkqB8nU4EAmt+8Xq359jSnH lNgLtWFeVJ7f/+aqUfWbjKJQZnvBuwnRYZ0J7jcOZ9BRF5CNys9ba9q5sFnrO4U2PJEh FoZ+eOd+4r5W1qyoNEaDZVj0MZAU7kNfGEE292pMfUxqcJQJHtalK8t355ASKOHoQx71 mQOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:references:user-agent:from:to:subject:date :in-reply-to:message-id:mime-version:content-transfer-encoding; bh=UOidZ3mfRBC2F7ySOmmj3g3IjKdY/VQ4CD9vtYW/7lc=; b=PBB2vxc/CkFPEo7BaFPMEkfsbgOwYZadKy940X9vWY7dHy/d0DquKzTpBY+bvF3F4R cBp6H3NnqMH/YXiG13N9SNx0X8mQZf6XgbAfDNMDbvydEAZ13oD788zdWZM5mxJ9NTmp ZsTo1Qxfkgyi/aIs32ZAVOrKMJw/EuR/rCEQT54ZkokefAWx+pyzymIA0nFBXy9gMAlV Y1Ilq6IYN1o/Fy9hX7Umk6JMOc85xuwM+n/RjHbygp3BVD6s2JbYMjdN1RAEhHHU9Hou YBKXNkFUZWenXcImyukujKqxCQ6QJ76jC/lDyGnNCHmmD2//eRUmEDsmH5WVbfkei79y RvKw== X-Gm-Message-State: AOAM530cDq26miSNDSdsz3j+Wquyf90+0BwATB0XCNnughBxErTAlzm3 X+ixVCi0sPSwZnawVT/1hEfpI8+rX9Q= X-Google-Smtp-Source: ABdhPJyghcJVxNvp0c6aH+U9CLHnPzFptriphj4Abj+KtCA7IpyI8iWJZ7Gl3KR7b5OTcGHihYVQsw== X-Received: by 2002:a17:902:7ecf:b0:149:956a:c2c7 with SMTP id p15-20020a1709027ecf00b00149956ac2c7mr4400907plb.40.1641907815820; Tue, 11 Jan 2022 05:30:15 -0800 (PST) Original-Received: from dingbat ([124.149.107.194]) by smtp.gmail.com with ESMTPSA id h1sm10447402pfi.109.2022.01.11.05.30.14 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Jan 2022 05:30:15 -0800 (PST) In-reply-to: X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:f8b0:4864:20::1031 (failed) Received-SPF: pass client-ip=2607:f8b0:4864:20::1031; envelope-from=theophilusx@gmail.com; helo=mail-pj1-x1031.google.com X-Spam_score_int: -12 X-Spam_score: -1.3 X-Spam_bar: - X-Spam_report: (-1.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action 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:284604 Archived-At: xenodasein--- via "Emacs development discussions." wr= ites: > Quoting: https://lists.gnu.org/archive/html/emacs-devel/2022-01/msg00794.= html >> ... >> At the end of the day, this seems like a non-problem driven by a >> belief/ideology that mixing user and auto-generated code is so wrong it >> has to be eliminated. If there was evidence of significant adverse >> impact to users due to this practice, change would be warranted. >> However, as it now stands, I cannot see how such change can be >> justified. > > All arguments against Drew's proposals so far converge at "it is better > to do nothing."=C2=A0 No, that is not what is being said. I'm saying "There is nothing needing to be done." It is an unnecessary change with little, if any, real benefit for users and which will have unnecessary/unwanted impact on some existing users.=20 > Why not propose something even better?=C2=A0 Better than what? Exactly what problem will this change address and how does this problem impact users and how does the proposed change mitigate that impact? > Throwing "where > is your evidence?" around is easy, but one must consider we are far from > the domain of scientific method here, or of law.=C2=A0 IF you propose a change, it has to be backed up with justification. Just saying it would be better is insufficient. So far, the justification seems to be it is better from a philosophical/theoretical standpoint not to mix user generated and auto-generated code in the same file, it could reduce accidental errors by the user editing the settings or the u= ser finds it confusing and the warning scares them. > Is existence of people > on Emacs related forums suggesting setting custom-file to /dev/null as a > good solution evidence enough?=C2=A0 I think all that is evidence of is bad advice. Why would you set your custom file to /dev/null? If you don't like custom, don't use it. If you do use it, that advice will likely just totally confuse you as now, if when you do use custom, it won't work. > > How about split of early-init/creation > of straight.el?=C2=A0 iWhat about it? How is it relevant to this proposed change? > What you call "belief/ideology" is known as intuition, > and it is the primary force behind any successful software.=C2=A0 > Or any > kind of invention, really. What is being proposed here is an impacting change to existing behaviour. Trying to claim such a change is 'innovative' or can be justified by intuition is simply insufficient. If it is a good change, then it should not be difficult to provide sufficient justification. Intuition can be both good and bad. There has to be some way to assess whether intuition (or an idea) is a good one - just saying it is intuition is not enough.=20=20 In over 30 years of working on software projects, some successful, some less so, I can say with confidence, those projects which failed were frequently those projects which did not manage change and were constantly making changes based on little else other than intuition. The projects which succeeded were the ones which correctly assessed which changes to do and which ones not to. Intuition seldom comes into it, but when it does, it is backed up with sufficient justification to offset any of the negative consequences.=20 > =C2=A0 > If only concern is the cost of change, why > not produce arguments for how to reduce that cost or to find a way > forward? Well that is easy. Don't perform change which has not been justified. When the change involved has impact to existing users, that impact needs to be justified. When the change modifies long standing behaviour, that modification needs to be justified. I also think it is poor form to basically tell me to come up with a better solution because I don't agree with the need for the change. Time would be better spent coming up with justification for the change rather than criticise me for not agreeing with you.=20