From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: On the rate of change [was: Another Emacs incompatibilty]
Date: Mon, 17 Aug 2020 16:21:41 +0200 [thread overview]
Message-ID: <87wo1x5p56.fsf@ebih.ebihd> (raw)
In-Reply-To: 20200817081232.GA13459@tuxteam.de
tomas wrote:
> It doesn't move, and then it's dead (heck even
> /bin/ls had to take ACLs into account at some point
> and SELinux at another). It does move too much, and
> then people flee in all directions (remember Jamie
> Zawinski's CADT?).
Well, no one is contemplating re-writing
Emacs, right?
I don't know if the rate of change is really the/a
problem. Can't you expand without breaking what is
there already? Isn't that what's been happening, 99%
of the time?
As for breaking what's there already, if it doesn't
make sense, just break it. If that breaks code that
relies on it as well, sure, that has to be changed as
well. But that's only a good thing!
If it _does_ make sense, leave it as it is, no doubt.
Who decides what makes sense and what doesn't?
People with skill and experience.
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
next prev parent reply other threads:[~2020-08-17 14:21 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 20:57 Another Emacs incompatibilty Torbjörn Granlund
2020-08-16 21:17 ` Stefan Monnier
2020-08-16 23:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-17 8:12 ` On the rate of change [was: Another Emacs incompatibilty] tomas
2020-08-17 14:21 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2020-08-17 15:20 ` tomas
2020-08-17 17:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-17 15:14 ` Another Emacs incompatibilty Torbjörn Granlund
2020-08-17 15:54 ` Robert Pluim
2020-08-17 16:08 ` Eli Zaretskii
2020-08-17 20:16 ` Torbjörn Granlund
2020-08-17 20:42 ` Stefan Monnier
2020-08-17 21:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-17 22:00 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-08-17 22:18 ` Eric Abrahamsen
2020-08-17 23:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-18 0:25 ` Eric Abrahamsen
2020-08-18 4:16 ` Stefan Monnier
2020-08-18 4:47 ` Eli Zaretskii
2020-08-18 5:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-18 5:36 ` Eli Zaretskii
2020-08-23 20:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-24 6:43 ` Alan Davis
2020-08-24 6:55 ` Eli Zaretskii
2020-08-24 23:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-24 14:31 ` Drew Adams
2020-08-24 23:24 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-25 0:53 ` Alan Davis
2020-08-25 4:09 ` Drew Adams
2020-08-25 4:14 ` Drew Adams
2020-08-25 4:30 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-25 5:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-25 5:46 ` Drew Adams
2020-08-25 6:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-25 5:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-24 15:31 ` Stefan Monnier
2020-08-24 23:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-18 15:47 ` Drew Adams
2020-08-18 16:45 ` Eric Abrahamsen
2020-08-18 16:52 ` Drew Adams
2020-08-18 17:50 ` Eric Abrahamsen
2020-08-18 17:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-17 16:31 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-08-17 16:49 ` Perry Smith
2020-08-17 16:54 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-08-17 17:22 ` Eli Zaretskii
2020-08-17 17:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-17 17:11 ` Eli Zaretskii
2020-08-17 17:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wo1x5p56.fsf@ebih.ebihd \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.