From: xenodasein--- via "Emacs development discussions." <emacs-devel@gnu.org>
To: theophilusx@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: [External] : Re: Default custom file was: Re: Propose to add setup-wizard.el to ELPA
Date: Tue, 11 Jan 2022 16:05:50 +0100 (CET) [thread overview]
Message-ID: <Mt8f7CT--3-2@tutanota.de> (raw)
In-Reply-To: <87h7aaz9gj.fsf@gmail.com>
Quoting: https://lists.gnu.org/archive/html/emacs-devel/2022-01/msg00821.html
> ...
> > All arguments against Drew's proposals so far converge at "it is better
> > to do nothing."
>
> 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.
>
> > Why not propose something even better?
>
> 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?
Well, I think we are getting there on this thread.
> > 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.
>
> 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 user
> 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?
>
> 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.
Yes, but such advice is then also evidence to that some users are
annoyed enough with the current (bad) behavior to do/talk about things
like that.
> > How about split of early-init/creation
> > of straight.el?
>
> iWhat about it? How is it relevant to this proposed change?
Suffice it to say that Customize and package.el modifying init.el
was used as a driving factor in creating some popular alternative
package managers.
> > What you call "belief/ideology" is known as intuition,
> > and it is the primary force behind any successful software.
> > 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.
>
> 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.
Apart from miscommunication, we actually think the same on this. Good
intuition and changes lead to success, bad to failure. I doubt "ones
which correctly assessed" used rigorous formal methods to arrive at their
decisions, I presume they did what we do on this list, talk over it.
> > 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.
But it is justified for many, AFAICT.
> 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.
What I find problematic here is that this is change would be a simplest
breaking change as possible, and we should try to get better at handling
these as there will be bigger ones, and we can't avoid them all the time.
I didn't intend to adress you directly if that is how it came out, but
this is a pattern I see a lot and wanted to express my opinion on it.
Thanks for giving a detailed response.
next prev parent reply other threads:[~2022-01-11 15:05 UTC|newest]
Thread overview: 157+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 6:13 Default custom file was: Re: Propose to add setup-wizard.el to ELPA Pedro Andres Aranda Gutierrez
2022-01-03 14:47 ` Robert Pluim
2022-01-04 6:13 ` Pedro Andres Aranda Gutierrez
2022-01-04 6:45 ` tomas
2022-01-04 7:29 ` Stefan Kangas
2022-01-04 10:10 ` tomas
2022-01-04 16:44 ` [External] : " Drew Adams
2022-01-04 17:09 ` tomas
2022-01-04 17:30 ` Drew Adams
2022-01-04 18:03 ` tomas
2022-01-04 18:27 ` Drew Adams
2022-01-04 18:41 ` tomas
2022-01-05 9:14 ` Stefan Kangas
2022-01-04 16:44 ` Drew Adams
2022-01-04 7:14 ` Stefan Kangas
2022-01-04 10:11 ` Robert Pluim
2022-01-04 10:30 ` Po Lu
2022-01-04 10:46 ` Robert Pluim
2022-01-04 10:59 ` Po Lu
2022-01-04 13:02 ` Robert Pluim
2022-01-04 11:11 ` Stefan Kangas
2022-01-04 12:23 ` LdBeth
2022-01-04 16:44 ` [External] : " Drew Adams
2022-01-04 13:08 ` Eli Zaretskii
2022-01-04 15:17 ` Stefan Kangas
2022-01-04 15:48 ` Robert Pluim
2022-01-04 15:57 ` Pedro Andres Aranda Gutierrez
2022-01-04 15:54 ` Pedro Andres Aranda Gutierrez
2022-01-04 16:44 ` [External] : " Drew Adams
2022-01-04 16:49 ` Robert Pluim
2022-01-04 17:14 ` Drew Adams
2022-01-04 17:32 ` Pedro Andres Aranda Gutierrez
2022-01-04 17:45 ` Drew Adams
2022-01-04 17:55 ` Robert Pluim
2022-01-04 18:24 ` Pedro Andres Aranda Gutierrez
2022-01-04 17:30 ` Eli Zaretskii
2022-01-04 17:35 ` Pedro Andres Aranda Gutierrez
2022-01-04 17:47 ` Eli Zaretskii
2022-01-04 17:57 ` Robert Pluim
2022-01-05 9:14 ` Stefan Kangas
2022-01-05 1:01 ` Po Lu
2022-01-05 7:03 ` Pedro Andres Aranda Gutierrez
2022-01-05 7:10 ` Pedro Andres Aranda Gutierrez
2022-01-05 7:22 ` Po Lu
2022-01-05 7:47 ` Drew Adams
2022-01-05 7:59 ` Po Lu
2022-01-05 9:17 ` LdBeth
2022-01-05 9:26 ` Robert Pluim
2022-01-05 10:54 ` Colin Baxter 😺
2022-01-05 11:24 ` Po Lu
2022-01-05 11:45 ` Pedro Andres Aranda Gutierrez
2022-01-05 12:09 ` Colin Baxter 😺
2022-01-05 13:04 ` Po Lu
2022-01-05 19:10 ` Drew Adams
2022-01-05 19:02 ` Drew Adams
2022-01-05 19:13 ` Eli Zaretskii
2022-01-05 19:36 ` Drew Adams
2022-01-05 9:35 ` Po Lu
2022-01-05 9:58 ` Pedro Andres Aranda Gutierrez
2022-01-05 10:58 ` xenodasein--- via Emacs development discussions.
2022-01-05 12:09 ` LdBeth
2022-01-05 12:57 ` Po Lu
2022-01-05 13:06 ` Eli Zaretskii
2022-01-05 15:58 ` Pedro Andres Aranda Gutierrez
2022-01-06 0:37 ` Po Lu
2022-01-06 7:21 ` Pedro Andres Aranda Gutierrez
2022-01-06 7:23 ` Po Lu
2022-01-06 7:33 ` Pedro Andres Aranda Gutierrez
2022-01-06 7:39 ` Po Lu
2022-01-06 8:58 ` Eli Zaretskii
2022-01-06 9:40 ` Po Lu
2022-01-06 9:45 ` Robert Pluim
2022-01-06 12:28 ` Colin Baxter 😺
2022-01-06 17:20 ` Drew Adams
2022-01-06 17:19 ` Drew Adams
2022-01-06 20:11 ` Tim Cross
2022-01-06 22:09 ` Drew Adams
2022-01-06 22:33 ` Tim Cross
2022-01-07 4:05 ` Drew Adams
2022-01-07 7:13 ` Tim Cross
2022-01-07 17:18 ` Drew Adams
2022-01-08 0:29 ` Tim Cross
2022-01-10 22:01 ` Drew Adams
2022-01-11 6:23 ` Tim Cross
2022-01-11 12:01 ` xenodasein--- via Emacs development discussions.
2022-01-11 12:10 ` Po Lu
2022-01-11 12:25 ` xenodasein--- via Emacs development discussions.
2022-01-11 12:42 ` tomas
[not found] ` <dbc302f1-a769-24d4-294d-e291b015229b@mnet-mail.de>
[not found] ` <Yd2W5BaccjjbJ6+q@tuxteam.de>
2022-01-11 15:23 ` xenodasein--- via Emacs development discussions.
[not found] ` <Yd2kAPRoYd37qCaN@tuxteam.de>
2022-01-11 16:05 ` xenodasein--- via Emacs development discussions.
2022-01-11 16:11 ` tomas
2022-01-12 0:46 ` Po Lu
2022-01-11 12:35 ` Tim Cross
2022-01-11 15:05 ` xenodasein--- via Emacs development discussions. [this message]
2022-01-11 20:57 ` Tim Cross
2022-01-11 13:27 ` Jean Louis
2022-01-07 0:52 ` Po Lu
2022-01-07 4:09 ` Drew Adams
2022-01-07 4:46 ` Po Lu
2022-01-07 5:58 ` Drew Adams
2022-01-07 7:04 ` Po Lu
2022-01-07 18:06 ` Drew Adams
2022-01-08 0:54 ` Po Lu
2022-01-08 3:13 ` LdBeth
2022-01-08 3:26 ` Po Lu
2022-01-08 7:19 ` Eli Zaretskii
2022-01-08 13:32 ` Add list of useful settings to setup wizard was: Re: Default custom file LdBeth
2022-01-08 14:12 ` Eli Zaretskii
2022-01-08 14:50 ` LdBeth
2022-01-08 14:39 ` Stefan Kangas
2022-01-08 15:30 ` LdBeth
2022-01-08 15:05 ` John Yates
2022-01-08 8:03 ` [External] : Re: Default custom file was: Re: Propose to add setup-wizard.el to ELPA tomas
2022-01-08 9:38 ` Po Lu
2022-01-08 10:39 ` xenodasein--- via Emacs development discussions.
2022-01-08 11:14 ` Po Lu
2022-01-08 12:35 ` xenodasein--- via Emacs development discussions.
2022-01-08 12:44 ` Po Lu
2022-01-08 12:59 ` xenodasein--- via Emacs development discussions.
2022-01-08 13:16 ` Po Lu
2022-01-08 13:24 ` xenodasein--- via Emacs development discussions.
2022-01-08 13:33 ` Po Lu
2022-01-08 13:44 ` xenodasein--- via Emacs development discussions.
2022-01-08 14:32 ` tomas
2022-01-08 14:46 ` xenodasein--- via Emacs development discussions.
2022-01-08 17:17 ` Corwin Brust
2022-01-08 18:26 ` xenodasein--- via Emacs development discussions.
[not found] ` <MtgbBbx--B-2@tutanota.de>
[not found] ` <MtqtDSN--3-2@tutanota.de>
2022-01-20 14:25 ` Corwin Brust
2022-01-10 19:20 ` [External] : " Drew Adams
2022-01-09 0:48 ` Po Lu
2022-01-08 13:35 ` =?gb18030?B?u9i4tKO6IFtFeHRlcm5hbF0gOiBSZTogRGVmYXVsdCBjdXN0b20gZmlsZSB3YXM6IFJlOiBQcm9wb3NlIHRvIGFkZCBzZXR1cC13aXphcmQuZWwgdG8gRUxQQQ==?= =?gb18030?B?emVyb2xlZQ==?=
2022-01-08 14:28 ` [External] : Re: Default custom file was: Re: Propose to add setup-wizard.el to ELPA tomas
2022-01-08 14:48 ` xenodasein--- via Emacs development discussions.
2022-01-08 11:42 ` tomas
2022-01-08 12:28 ` xenodasein--- via Emacs development discussions.
2022-01-10 19:17 ` Drew Adams
2022-01-10 22:02 ` Drew Adams
2022-01-12 4:55 ` Richard Stallman
2022-01-12 8:58 ` xenodasein--- via Emacs development discussions.
2022-01-12 13:18 ` Eli Zaretskii
2022-01-12 5:09 ` Po Lu
2022-01-07 0:49 ` Po Lu
2022-01-07 4:09 ` Drew Adams
2022-01-07 4:42 ` Po Lu
2022-01-07 6:38 ` Pedro Andres Aranda Gutierrez
2022-01-07 8:43 ` Robert Pluim
2022-01-07 9:38 ` Pedro Andres Aranda Gutierrez
2022-01-07 17:17 ` Drew Adams
2022-01-07 17:12 ` Drew Adams
2022-01-06 17:19 ` Drew Adams
2022-01-07 0:48 ` Po Lu
2022-01-07 4:09 ` Drew Adams
2022-01-07 6:18 ` tomas
2022-01-07 18:06 ` Drew Adams
2022-01-06 16:17 ` Drew Adams
2022-01-05 7:43 ` Drew Adams
2022-01-04 16:43 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Mt8f7CT--3-2@tutanota.de \
--to=emacs-devel@gnu.org \
--cc=theophilusx@gmail.com \
--cc=xenodasein@tutanota.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).