From: Robert Pluim <rpluim@gmail.com>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Implicit assumptions in the latest discussions
Date: Thu, 17 Sep 2020 16:01:17 +0200 [thread overview]
Message-ID: <m2k0ws5wpe.fsf@gmail.com> (raw)
In-Reply-To: <1bc3251a-7b36-f151-7fc6-9ecf2639bb9f@grinta.net> (Daniele Nicolodi's message of "Thu, 17 Sep 2020 15:30:48 +0200")
>>>>> On Thu, 17 Sep 2020 15:30:48 +0200, Daniele Nicolodi <daniele@grinta.net> said:
Daniele> Hello,
Daniele> I admit I just read a minimal part of the posts in the current threads
Daniele> about making Emacs simpler, or friendlier, or more "modern" (for a
Daniele> definition of modern very different to mine). However, I would like to
Daniele> express my doubts about the assumptions implicit in these discussions.
Daniele> These assumptions seem to be:
Daniele> 1. Emacs would be better if it had a larger user base or the Emacs users
Daniele> would be better served by an Emacs that appeals to a larger user base. I
Daniele> think that this can be true only as far as another assumption hold,
Daniele> namely that with a larger user base there would be more manpower to work
Daniele> on Emacs itself, thus Emacs will become better because more people is
Daniele> hacking on it.
Daniele> I don't think there can be any correlation between the number of users
Daniele> of Emacs and the number of hackers interesting in working on it. If the
Daniele> end goal is to make Emacs development more sustainable, an easier way to
Daniele> get there would be to modernize the development practices used to work
Daniele> on Emacs itself. However, this is a much harder (social) problem to solve.
Youʼre falling into the "the 'modern' gitlab/github etc dev practices
are better" fallacy here. Theyʼre more *familiar* to certain people,
but I donʼt really like them, because too much of the interaction is
done with a browser (and Iʼm sure Iʼm not alone). See discussions on
this list about moving to such workflows whilst ensuring that email
can still be used.
Daniele> 2. Users are not drawn to try Emacs because what Emacs is and for his
Daniele> reputation, but because they expect Emacs to be like other editors.
Daniele> I think that who chooses Emacs, does so because of what Emacs is and
Daniele> what it has been in its long history, not because they expect something
Daniele> different. If they expect something different, Emacs has an enormous
Daniele> technical disadvantage compared to younger editors that are based on
Daniele> different technologies and that do not want (need?) to keep
Daniele> compatibility if an incredibly long history.
Daniele> Probably there are better thing that can be done to make the experience
Daniele> of these users better than providing "simplified" Emacs environments,
Daniele> because the users that choose Emacs don't want a simplified Emacs, they
Daniele> want better ways to access the power of Emacs.
Daniele> Having "simplified" modes also poses the problem of allowing the users
Daniele> to "graduate" from the simplified environment to the full blown one. I
Daniele> haven't see this discussed.
I think "simplified" is not the goal here, but "more familiar". Unlike
development practices, I see no issue here with offering that kind of
experience by default, since I can turn it off easily. The
"graduation" problem exists, but thatʼs easily solved with
documentation :-)
Daniele> 3. Emacs is perfect as it is, but the users do not understand it.
Daniele> I feel that a lot of the discussions are centered toward having ways to
Daniele> simplify Emacs to make it more appealing to new users or to some very
Daniele> specific classes of prospective users. Wouldn't it be more productive
Daniele> and wouldn't it be better for who already has invested in Emacs (namely
Daniele> the current users) to discuss ways to make Emacs better for everyone?
Daniele> For example, GNU/Linux is the platform where Emacs should run best,
Daniele> however, as far as I know, there is currently no way to run Emacs on a
Daniele> Wayland compositor, and Wayland is the future of graphical interfaces on
Daniele> GNU/Linux. Also, some of the complexity of hacking on Emacs, comes from
Daniele> supporting a wide range of graphical toolkits. Wouldn't it be a
Daniele> worthwhile goal to support a graphical toolkit that works on Wayland,
Daniele> and then make it the only one supported (at least on GNU/Linux) and
Daniele> redirect some hacking energy into making this solution a good solution
Daniele> for everyone (hacking on the toolkit itself if necessary)? This would be
Daniele> much more important to keep Emacs relevant in a few years from now than
Daniele> a Emacs-simplified-mode.
Thereʼs an effort underway already to port emacs to 'pure' gtk, which
allows running directly on Wayland. See eg
<https://github.com/fejfighter/emacs>.
Daniele> While the use of a specific graphical toolkit may seems a technical
Daniele> issue far from the current discussions, I would like to point out that
Daniele> also this is mostly a "social" issue: removing support for other
Daniele> toolkits will affect those that for one reason or another prefer to use
Daniele> Motif Emacs.
There are people who are very attached to using the Lucid toolkit, and
they have valid reasons. Once the 'pure' gtk is in, thereʼs no reason
to remove Lucid support, but there'd also be no reason to enhance it.
Robert
next prev parent reply other threads:[~2020-09-17 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 13:30 Implicit assumptions in the latest discussions Daniele Nicolodi
2020-09-17 14:01 ` Robert Pluim [this message]
2020-09-17 14:45 ` Daniele Nicolodi
2020-09-17 15:04 ` Arthur Miller
2020-09-17 15:09 ` Daniel Martín
2020-09-17 15:29 ` Caio Henrique
2020-09-17 15:32 ` Robert Pluim
2020-09-17 17:41 ` Eli Zaretskii
2020-09-17 19:31 ` Mingde (Matthew) Zeng
2020-09-18 7:45 ` Emanuel Berg via Emacs development discussions.
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=m2k0ws5wpe.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=daniele@grinta.net \
--cc=emacs-devel@gnu.org \
/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.